Hi, I’ve created the following repos for 3.6.4 release and going to push them to apache. Should I use 3.6.x branch and create a new 3.6.4 tag or 3.6.4 branch?
android: https://github.com/MSOpenTech/cordova-android/commits/3.6.4 • CB-6511 Fixes build for android when app name contains unicode characters • CB-7579 Fix run script's ability to use non-arch-specific APKs windows: https://github.com/MSOpenTech/cordova-windows/commits/3.6.4 • CB-7617 Deploy on WP8.1 incorrectly handles --target name wp8: https://github.com/MSOpenTech/cordova-wp8/commits/3.6.4 • CB-7616 Deploy on WP8 fails to run specific target LIB: https://github.com/MSOpenTech/cordova-lib/commits/0.21.14 • CB-7578 Windows. Fix platform name reported by pre_package hook • CB-7576 Support 'windows' merges folder for Windows platform The code is based on previous 3.6 release with some specific fixes added, please let me know if we want to release more. Thx! Sergey -----Original Message----- From: Carlos Santana [mailto:csantan...@gmail.com] Sent: Friday, September 26, 2014 5:56 AM To: dev@cordova.apache.org Subject: Re: Next Cordova Release Steven, If it's not too much extra work lets try to keep travis-ci and appveyor most of the time green. Now they show red. if cordova-lib depends on npm cordova-js, then land the changes in cordova-js let's vote and publish, and then land changes in cordova-lib keeping CI always green. Again if it's not too overhead. I also see that ci.cordova.io is red on cli, not sure what the problem is there something about parsing package.json On Thu, Sep 25, 2014 at 1:11 PM, Sergey Grebnov (Akvelon) < v-seg...@microsoft.com> wrote: > That helped, thx a lot, Steven! > > -----Original Message----- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Thursday, September 25, 2014 8:34 PM > To: dev@cordova.apache.org > Subject: Re: Next Cordova Release > > Make sure you have cordovajs npm linked into Cordova-lib. My push to > lib yesterday has a few failing browserify tests unless you link > Cordova-JS master in your node modules folder. > > Not sure if this is what you are seeing but if it is, might save you > some time. > > On Thursday, September 25, 2014, Sergey Grebnov (Akvelon) < > v-seg...@microsoft.com> wrote: > > > Rebased hooks implementation on top of master; see some unit tests > > failures, investigating.. > > https://github.com/apache/cordova-lib/pull/55 > > > > Thx! > > Sergey > > -----Original Message----- > > From: Carlos Santana [mailto:csantan...@gmail.com <javascript:;>] > > Sent: Thursday, September 25, 2014 1:26 AM > > To: dev@cordova.apache.org <javascript:;> > > Subject: Re: Next Cordova Release > > > > yes now it's the time to keep the train running, as for cordova hook > > it's a tool feature compatible with 3.6.x platforms. I would deliver > > in cordova-lib 3.6.x train. > > > > let's keep the train of releases keep running at their own pace > > > > On Wed, Sep 24, 2014 at 5:18 PM, Steven Gill <stevengil...@gmail.com > > <javascript:;>> wrote: > > > > > I think this is a good time to test out independent platform releases! > > > > > > Let me know when you are ready to release either of those fixes > > > and I can work with you to get it out! > > > > > > -Steve > > > > > > On Wed, Sep 24, 2014 at 11:53 AM, Archana Naik > > > <naik.arch...@gmail.com <javascript:;>> > > > wrote: > > > > > > > Wow...good to know we are already starting about next > > > > releases...We are still testing 3.6.3 here. :) > > > > > > > > And yes, Parashuram if something is fixed in android we would > > > > like to > > > adopt > > > > in amazon-fireos as well. > > > > > > > > Archana > > > > > > > > On Wed, Sep 24, 2014 at 11:34 AM, Parashuram Narasimhan (MS OPEN > > > > TECH) < panar...@microsoft.com <javascript:;>> wrote: > > > > > > > > > Marcel, thank you for driving the Cordova tools release - 3.6.3. > > > > > > > > > > There are a few bugs that we discovered in this release that > > > > > we would > > > > like > > > > > to fix. These are not major to require a full major version > > > > > bump, but regressions that should be fixed. The bugs we would > > > > > like to get into a release are > > > > > > > > > > > > > > > 1. Windows and Wp8 platform > > > > > > > > > > a. --target flag is not supported in the Windows platforms. > > Given > > > > > the new support for Windows 8, Windows 8.1 and Windows Phone > > > > > 8.1 this > > > is > > > > > important as it lets users choose a way to run the app on > > > > > specific > > > > emulators > > > > > > > > > > 2. Android > > > > > > > > > > a. The --nobuild flag for run seems to be broken now. > > > > > > > > > > b. If possible we would also like to get the patch for Cordova > > > > > activity name so that Unicode characters can be used for > > > > > Android > > apps. > > > > > > > > > > i. > > > > > Does this change also need to be made in Amazon FireOS? > > > > > Archana, should > > > > we > > > > > send in a pull request for that ? > > > > > > > > > > 3. Tools > > > > > > > > > > a. The community has agreed on the hooks implementation and > > this > > > is > > > > > done now. > > > > > > > > > > Will the next release be 4.0, and when is it planned for? If > > > > > it is a > > > > month > > > > > away, can we cherry pick these changes into 3.6.3 and make a > > > > > 3.6.4 > > > > release > > > > > before that ? Are there other bug fixes that people want to go > > > > > in a > > > next > > > > > release. > > > > > > > > > > We can volunteer to do the next release (with consultation > > > > > from Marcel > > > if > > > > > possible, since he is now knows the release process). > > > > > > > > > > > > > > > > > > > > -- > > Carlos Santana > > <csantan...@gmail.com <javascript:;>> > > > -- Carlos Santana <csantan...@gmail.com>
