cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Grebnov (Akvelon)" <>
Subject RE: [Vote] 4.2.0 Windows Release
Date Thu, 12 Nov 2015 08:41:51 GMT
The vote has now closed. The results are:

Positive Binding Votes: 3

Alexander Sorokin
Vladimir Kotikov
Sergey Grebnov

Negative Binding Votes: 0

The vote has passed.


-----Original Message-----
From: Vladimir Kotikov (Akvelon) [] 
Sent: Wednesday, November 11, 2015 12:42 PM
Subject: RE: [Vote] 4.2.0 Windows Release

I vote +1

* Verified release candidate with 'coho verify-archive'
* Verified that blank app created and built successfully
* Verified that upgrade from previous version succeeds

Best regards, Vladimir

-----Original Message-----
From: Alexander Sorokin (Akvelon) [] 
Sent: Monday, November 9, 2015 6:52 PM
To: '' <>
Subject: RE: [Vote] 4.2.0 Windows Release

I vote +1.

* Verified archives via `coho verify-archive`

* Verified tags manually

* Verified that blank app creates correctly with platform

* Verified that blank app can be successfully built and ran

* Verified compatibility with core plugins (ran autotests for both release and master plugin

* Verified release notes

Additional checks:

* Verified version

* Verified line breaks


Alexander Sorokin

From: Sergey Grebnov (Akvelon)
Sent: Saturday, November 7, 2015 4:37 PM
To: ''
Subject: RE: [Vote] 4.2.0 Windows Release

Re-sending Vote email using correct platform name and version (4.2.0 Windows Release).

Please review and vote on this 4.2.0 Windows Release by replying to this email (and keep discussion
on the DISCUSS thread)

Release issue:

The archive has been published to dist/dev:

The package was published from its corresponding git tag:
    cordova-windows: 4.2.0 (b56900f1d2)

Note that you can test it out via:

    cordova platform add

Upon a successful vote I will upload the archive to dist/, publish it to npm, and post the
blog post.

Voting guidelines:

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible
* Ensured continuous build was green when repo was tagged
* Run mobile spec tests


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message