[DISCUSS] cordova-fetch patch release (tools)

2018-07-29 Thread Chris Brody
Does anyone have any reason to delay a cordova-fetch patch release (tools)? Any outstanding patches to land? If not, I will start the release tomorrow (or the day after). The versions to be released are: - cordova-fetch@1.3.1

[VOTE] cordova-osx 4.0.2 patch release

2018-07-29 Thread Chris Brody
Please review and vote on this 4.0.2 cordova-osx (macOS) patch release by replying to this email (and keep discussion on the DISCUSS thread). Release issue: https://issues.apache.org/jira/browse/CB-14228 The archive has been published to dist/dev:

[VOTE] cordova-windows@6.0.1 patch release (subject fixed)

2018-07-29 Thread Chris Brody
Please review and vote on this 6.0.1 Windows patch release by replying to this email (and keep discussion on the DISCUSS thread). Release issue: https://issues.apache.org/jira/browse/CB-14226 The archive has been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-14226/

Re: [VOTE] cordova-wndroid@6.0.1 patch release

2018-07-29 Thread Chris Brody
This VOTE thread is hereby cancelled, correctly titled VOTE thread is coming next. On Sun, Jul 29, 2018 at 10:48 PM Shazron wrote: > > The subject says "[VOTE] cordova-wndroid@6.0.1 patch release". A bit > ambiguous, I propose re-doing the vote. > On Sat, Jul 28, 2018 at 7:23 AM Chris Brody

Nightly build #804 for cordova has failed

2018-07-29 Thread Apache Jenkins Server
Nightly build #804 for cordova has failed. Please check failure details on build details page at https://builds.apache.org/job/cordova-nightly/804/ You can also take a look at build console: https://builds.apache.org/job/cordova-nightly/804/consoleFull - Jenkins for Apache Cordova

Re: [VOTE] cordova-wndroid@6.0.1 patch release

2018-07-29 Thread Shazron
The subject says "[VOTE] cordova-wndroid@6.0.1 patch release". A bit ambiguous, I propose re-doing the vote. On Sat, Jul 28, 2018 at 7:23 AM Chris Brody wrote: > > Please review and vote on this 6.0.1 Windows patch release by replying > to this email (and keep discussion on the DISCUSS thread). >