You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com> on 2014/09/24 20:34:12 UTC

Next Cordova Release

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).

Re: Next Cordova Release

Posted by Marcel Kinard <cm...@gmail.com>.
My personal preference is to first commit to master, then cherry-pick to the desired branch. That way master is always current.

On Sep 26, 2014, at 6:20 PM, Jesse <pu...@gmail.com> wrote:

> Yes, 3.6.x branch and tag it when it is ready.
> then they can also be cherry-picked into master, or you could commit them
> into master, and cherry-pick them into the 3.6.x branch ...


Re: Next Cordova Release

Posted by Carlos Santana <cs...@gmail.com>.
Go Steve !!! It looks like you had a great vacation all energized

Should we make cordova-lib also 3.7.0 ? cordova-cli is essentially
cordova-lib in most part. Also for us to remember that cordova-cli 3.7.x
depends on cordova-lib 3.7.x and keep them green son on going forward.
Allowing for releases and branch consistency, like having a cordova-lib
branches 3.7.x and 4.0.x

+1 on keeping dependencies fresh and pinned regardless of the shrinkwrap
outcome.

On Monday, September 29, 2014, Marcel Kinard <cm...@gmail.com> wrote:

> Thanks!
>
> Heads-up that doing the shrinkwrap made the tools release more complicated.
>
> On Sep 29, 2014, at 4:23 PM, Steven Gill <stevengill97@gmail.com
> <javascript:;>> wrote:
>
> > I can take it. Gives me a chance to review changes to the process when I
> > was away. I'll do it after I get the first vote started
>
>

-- 
Carlos Santana
<cs...@gmail.com>

Re: Next Cordova Release

Posted by Marcel Kinard <cm...@gmail.com>.
Thanks!

Heads-up that doing the shrinkwrap made the tools release more complicated.

On Sep 29, 2014, at 4:23 PM, Steven Gill <st...@gmail.com> wrote:

> I can take it. Gives me a chance to review changes to the process when I
> was away. I'll do it after I get the first vote started


Re: Next Cordova Release

Posted by Steven Gill <st...@gmail.com>.
I can take it. Gives me a chance to review changes to the process when I
was away. I'll do it after I get the first vote started

On Monday, September 29, 2014, Marcel Kinard <cm...@gmail.com> wrote:

> Steve, I was going to start a plugins release today, since I got busy on
> Friday.
>
> Do you want to roll a plugins release into what you are already doing, or
> would you prefer I continue with it as I originally volunteered?
>
> On Sep 29, 2014, at 2:03 PM, Steven Gill <stevengill97@gmail.com
> <javascript:;>> wrote:
>
> > Alright lets do this!
> >
> > Releasing:
> > Cordova-Android 3.6.4
> > Cordova-Windows 3.6.4
> > Cordova-WP8 3.6.4
> > Cordova-Browser 3.6.0
> >
> > Cordova-Lib 0.21.14
> > Cordova-JS 3.7.0
> > Cordova-Plugman 0.22.11
> > Cordova-CLI 3.7.0
> > I think it is a good time to drop the cadVer-SemVer versioning for the
> CLI.
> > Lets just make it SemVer but start from 3.7.0
> >
> > 1) Release issue:
> > - coho create-release-bug is supposed to be used for cadence releases. It
> > won't make sense when we aren't release every platform. We will have to
> > create the release issue manually. This is what we have been doing for
> > tools releases for a while now.
> >
> > 2) Platform version files should be bumped using coho. Coho also goes in
> > and changes the version script output for many of the platforms (all
> except
> > windows ones last I saw)
> >
> > 3) I like this idea. I personally think we should test it thoroughly
> before
> > we push it live though. Not sure what problems might arise. If people
> feel
> > confident with releasing this change and have tested it, I won't stand in
> > the way of it being released.
> >
> > I recently merged in my Indy platform release work. I want to take this
> > release to go through the process and fix any problems that come up. You
> > can see the doc at
> >
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
> .
> > Sergey, I can work with you on this or, if you don't mind, I can take
> over
> > from here.
> >
> > -Steve
> >
> >
> > On Mon, Sep 29, 2014 at 2:45 AM, Sergey Grebnov (Akvelon) <
> > v-segreb@microsoft.com <javascript:;>> wrote:
> >
> >> Hi, here are release branches:
> >>
> >> https://github.com/apache/cordova-cli/tree/rb_3.6.4-0.21.14
> >> https://github.com/apache/cordova-lib/tree/rb_0.21.14
> >>
> >> https://github.com/apache/cordova-android/tree/3.6.x
> >> https://github.com/apache/cordova-windows/tree/3.6.x
> >> https://github.com/apache/cordova-wp8/tree/3.6.x
> >>
> >> I've not updated versions and added tags due to the following
> >> questions/issues:
> >>
> >> 1. I wanted to create release issue to use while updating version files
> >> but it is not possible since we don't have 3.6.4 version in JIRA. Could
> >> someone create it?
> >>    λ coho create-release-bug --version=3.6.4
> >>   Cannot find version ID number in JIRA related to "root" version
> string:
> >> 3.6.4
> >>
> >> 2. Is it ok to bump platform version files manually? - I see we mixed
> coho
> >> and manual edits during 3.6.3 release.
> >>
> >> 3. What do you think if we change depending platform versions in
> >> platforms.js [1] to 3.6 (or 3.6.x) instead of 3.6.3/4?  This way we
> will be
> >> able to release 3.6.4 for ios, bb, other platforms w/o TOOLS release.
> Same
> >> if we want to release 3.6.5 version of some platform later.
> >>        * npm cache logic used in LIB seems to correctly handle this case
> >> and download updated platform version when it is available on npm
> >>        * for --usegit option we can have 3.6 tag along with 3.6.3 and
> >> 3.6.4  so this will work as well
> >>
> >> [1]
> >>
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platforms.js
> >>
> >> Thx!
> >> Sergey
> >>
> >> -----Original Message-----
> >> From: Jesse [mailto:purplecabbage@gmail.com <javascript:;>]
> >> Sent: Saturday, September 27, 2014 2:20 AM
> >> To: dev@cordova.apache.org <javascript:;>
> >> Subject: Re: Next Cordova Release
> >>
> >> Yes, 3.6.x branch and tag it when it is ready.
> >> then they can also be cherry-picked into master, or you could commit
> them
> >> into master, and cherry-pick them into the 3.6.x branch ...
> >>
> >> @purplecabbage
> >> risingj.com
> >>
> >> On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <cmarcelk@gmail.com
> <javascript:;>> wrote:
> >>
> >>> I'd suggest pushing the commits on to the end of the 3.6.x branch, and
> >>> then tag it 3.6.4.
> >>>
> >>> On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) <
> >>> v-segreb@microsoft.com <javascript:;>> wrote:
> >>>
> >>>> 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?
> >>>
> >>>
> >>
>
>

Re: Next Cordova Release

Posted by Marcel Kinard <cm...@gmail.com>.
Steve, I was going to start a plugins release today, since I got busy on Friday.

Do you want to roll a plugins release into what you are already doing, or would you prefer I continue with it as I originally volunteered?

On Sep 29, 2014, at 2:03 PM, Steven Gill <st...@gmail.com> wrote:

> Alright lets do this!
> 
> Releasing:
> Cordova-Android 3.6.4
> Cordova-Windows 3.6.4
> Cordova-WP8 3.6.4
> Cordova-Browser 3.6.0
> 
> Cordova-Lib 0.21.14
> Cordova-JS 3.7.0
> Cordova-Plugman 0.22.11
> Cordova-CLI 3.7.0
> I think it is a good time to drop the cadVer-SemVer versioning for the CLI.
> Lets just make it SemVer but start from 3.7.0
> 
> 1) Release issue:
> - coho create-release-bug is supposed to be used for cadence releases. It
> won't make sense when we aren't release every platform. We will have to
> create the release issue manually. This is what we have been doing for
> tools releases for a while now.
> 
> 2) Platform version files should be bumped using coho. Coho also goes in
> and changes the version script output for many of the platforms (all except
> windows ones last I saw)
> 
> 3) I like this idea. I personally think we should test it thoroughly before
> we push it live though. Not sure what problems might arise. If people feel
> confident with releasing this change and have tested it, I won't stand in
> the way of it being released.
> 
> I recently merged in my Indy platform release work. I want to take this
> release to go through the process and fix any problems that come up. You
> can see the doc at
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md.
> Sergey, I can work with you on this or, if you don't mind, I can take over
> from here.
> 
> -Steve
> 
> 
> On Mon, Sep 29, 2014 at 2:45 AM, Sergey Grebnov (Akvelon) <
> v-segreb@microsoft.com> wrote:
> 
>> Hi, here are release branches:
>> 
>> https://github.com/apache/cordova-cli/tree/rb_3.6.4-0.21.14
>> https://github.com/apache/cordova-lib/tree/rb_0.21.14
>> 
>> https://github.com/apache/cordova-android/tree/3.6.x
>> https://github.com/apache/cordova-windows/tree/3.6.x
>> https://github.com/apache/cordova-wp8/tree/3.6.x
>> 
>> I've not updated versions and added tags due to the following
>> questions/issues:
>> 
>> 1. I wanted to create release issue to use while updating version files
>> but it is not possible since we don't have 3.6.4 version in JIRA. Could
>> someone create it?
>>    λ coho create-release-bug --version=3.6.4
>>   Cannot find version ID number in JIRA related to "root" version string:
>> 3.6.4
>> 
>> 2. Is it ok to bump platform version files manually? - I see we mixed coho
>> and manual edits during 3.6.3 release.
>> 
>> 3. What do you think if we change depending platform versions in
>> platforms.js [1] to 3.6 (or 3.6.x) instead of 3.6.3/4?  This way we will be
>> able to release 3.6.4 for ios, bb, other platforms w/o TOOLS release. Same
>> if we want to release 3.6.5 version of some platform later.
>>        * npm cache logic used in LIB seems to correctly handle this case
>> and download updated platform version when it is available on npm
>>        * for --usegit option we can have 3.6 tag along with 3.6.3 and
>> 3.6.4  so this will work as well
>> 
>> [1]
>> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platforms.js
>> 
>> Thx!
>> Sergey
>> 
>> -----Original Message-----
>> From: Jesse [mailto:purplecabbage@gmail.com]
>> Sent: Saturday, September 27, 2014 2:20 AM
>> To: dev@cordova.apache.org
>> Subject: Re: Next Cordova Release
>> 
>> Yes, 3.6.x branch and tag it when it is ready.
>> then they can also be cherry-picked into master, or you could commit them
>> into master, and cherry-pick them into the 3.6.x branch ...
>> 
>> @purplecabbage
>> risingj.com
>> 
>> On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <cm...@gmail.com> wrote:
>> 
>>> I'd suggest pushing the commits on to the end of the 3.6.x branch, and
>>> then tag it 3.6.4.
>>> 
>>> On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) <
>>> v-segreb@microsoft.com> wrote:
>>> 
>>>> 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?
>>> 
>>> 
>> 


Re: Next Cordova Release

Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
Awesome, thanks steve. Please do let us know if there is anything we can
help you with. 

On 9/29/14, 11:03 AM, "Steven Gill" <st...@gmail.com> wrote:

>Alright lets do this!
>
>Releasing:
>Cordova-Android 3.6.4
>Cordova-Windows 3.6.4
>Cordova-WP8 3.6.4
>Cordova-Browser 3.6.0
>
>Cordova-Lib 0.21.14
>Cordova-JS 3.7.0
>Cordova-Plugman 0.22.11
>Cordova-CLI 3.7.0
>I think it is a good time to drop the cadVer-SemVer versioning for the
>CLI.
>Lets just make it SemVer but start from 3.7.0
>
>1) Release issue:
> - coho create-release-bug is supposed to be used for cadence releases. It
>won't make sense when we aren't release every platform. We will have to
>create the release issue manually. This is what we have been doing for
>tools releases for a while now.
>
>2) Platform version files should be bumped using coho. Coho also goes in
>and changes the version script output for many of the platforms (all
>except
>windows ones last I saw)
>
>3) I like this idea. I personally think we should test it thoroughly
>before
>we push it live though. Not sure what problems might arise. If people feel
>confident with releasing this change and have tested it, I won't stand in
>the way of it being released.
>
>I recently merged in my Indy platform release work. I want to take this
>release to go through the process and fix any problems that come up. You
>can see the doc at
>https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-
>process.md.
>Sergey, I can work with you on this or, if you don't mind, I can take over
>from here.
>
>-Steve
>
>
>On Mon, Sep 29, 2014 at 2:45 AM, Sergey Grebnov (Akvelon) <
>v-segreb@microsoft.com> wrote:
>
>> Hi, here are release branches:
>>
>> https://github.com/apache/cordova-cli/tree/rb_3.6.4-0.21.14
>> https://github.com/apache/cordova-lib/tree/rb_0.21.14
>>
>> https://github.com/apache/cordova-android/tree/3.6.x
>> https://github.com/apache/cordova-windows/tree/3.6.x
>> https://github.com/apache/cordova-wp8/tree/3.6.x
>>
>> I've not updated versions and added tags due to the following
>> questions/issues:
>>
>> 1. I wanted to create release issue to use while updating version files
>> but it is not possible since we don't have 3.6.4 version in JIRA. Could
>> someone create it?
>>     λ coho create-release-bug --version=3.6.4
>>    Cannot find version ID number in JIRA related to "root" version
>>string:
>> 3.6.4
>>
>> 2. Is it ok to bump platform version files manually? - I see we mixed
>>coho
>> and manual edits during 3.6.3 release.
>>
>> 3. What do you think if we change depending platform versions in
>> platforms.js [1] to 3.6 (or 3.6.x) instead of 3.6.3/4?  This way we
>>will be
>> able to release 3.6.4 for ios, bb, other platforms w/o TOOLS release.
>>Same
>> if we want to release 3.6.5 version of some platform later.
>>         * npm cache logic used in LIB seems to correctly handle this
>>case
>> and download updated platform version when it is available on npm
>>         * for --usegit option we can have 3.6 tag along with 3.6.3 and
>> 3.6.4  so this will work as well
>>
>> [1]
>> 
>>https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova
>>/platforms.js
>>
>> Thx!
>> Sergey
>>
>> -----Original Message-----
>> From: Jesse [mailto:purplecabbage@gmail.com]
>> Sent: Saturday, September 27, 2014 2:20 AM
>> To: dev@cordova.apache.org
>> Subject: Re: Next Cordova Release
>>
>> Yes, 3.6.x branch and tag it when it is ready.
>> then they can also be cherry-picked into master, or you could commit
>>them
>> into master, and cherry-pick them into the 3.6.x branch ...
>>
>> @purplecabbage
>> risingj.com
>>
>> On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <cm...@gmail.com>
>>wrote:
>>
>> > I'd suggest pushing the commits on to the end of the 3.6.x branch, and
>> > then tag it 3.6.4.
>> >
>> > On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) <
>> > v-segreb@microsoft.com> wrote:
>> >
>> > > 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?
>> >
>> >
>>


RE: Next Cordova Release

Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
> Sergey, I can work with you on this or, if you don't mind, I can take 
> over from here.

Yes, please go ahead. Thank you, Steve!

-----Original Message-----
From: iclelland@google.com [mailto:iclelland@google.com] On Behalf Of Ian Clelland
Sent: Monday, September 29, 2014 10:16 PM
To: dev@cordova.apache.org
Subject: Re: Next Cordova Release

On Mon, Sep 29, 2014 at 2:03 PM, Steven Gill <st...@gmail.com> wrote:

> Alright lets do this!
>

Don't stop the train! :)

>
> Releasing:
> Cordova-Android 3.6.4
> Cordova-Windows 3.6.4
> Cordova-WP8 3.6.4
> Cordova-Browser 3.6.0
>
> Cordova-Lib 0.21.14
> Cordova-JS 3.7.0
> Cordova-Plugman 0.22.11
> Cordova-CLI 3.7.0
> I think it is a good time to drop the cadVer-SemVer versioning for the CLI.
> Lets just make it SemVer but start from 3.7.0
>

+1 -- Sooner or later, that not-quite-semver is going to bite us hard.
Better to get rid of it now, I think.



>
> 1) Release issue:
>  - coho create-release-bug is supposed to be used for cadence 
> releases. It won't make sense when we aren't release every platform. 
> We will have to create the release issue manually. This is what we 
> have been doing for tools releases for a while now.
>
> 2) Platform version files should be bumped using coho. Coho also goes 
> in and changes the version script output for many of the platforms 
> (all except windows ones last I saw)
>
> 3) I like this idea. I personally think we should test it thoroughly 
> before we push it live though. Not sure what problems might arise. If 
> people feel confident with releasing this change and have tested it, I 
> won't stand in the way of it being released.
>

Same here -- patch releases should be for bug fixes with no compatibility issues, so as long as we test well, then "3.6.latest" is a better policy than "3.6.4 exactly", I'd say.

Ian


>
> I recently merged in my Indy platform release work. I want to take 
> this release to go through the process and fix any problems that come 
> up. You can see the doc at
>
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-rele
> ase-process.md
> .
> Sergey, I can work with you on this or, if you don't mind, I can take 
> over from here.
>
> -Steve
>
>
> On Mon, Sep 29, 2014 at 2:45 AM, Sergey Grebnov (Akvelon) < 
> v-segreb@microsoft.com> wrote:
>
> > Hi, here are release branches:
> >
> > https://github.com/apache/cordova-cli/tree/rb_3.6.4-0.21.14
> > https://github.com/apache/cordova-lib/tree/rb_0.21.14
> >
> > https://github.com/apache/cordova-android/tree/3.6.x
> > https://github.com/apache/cordova-windows/tree/3.6.x
> > https://github.com/apache/cordova-wp8/tree/3.6.x
> >
> > I've not updated versions and added tags due to the following
> > questions/issues:
> >
> > 1. I wanted to create release issue to use while updating version 
> > files but it is not possible since we don't have 3.6.4 version in 
> > JIRA. Could someone create it?
> >     λ coho create-release-bug --version=3.6.4
> >    Cannot find version ID number in JIRA related to "root" version
> string:
> > 3.6.4
> >
> > 2. Is it ok to bump platform version files manually? - I see we 
> > mixed
> coho
> > and manual edits during 3.6.3 release.
> >
> > 3. What do you think if we change depending platform versions in 
> > platforms.js [1] to 3.6 (or 3.6.x) instead of 3.6.3/4?  This way we 
> > will
> be
> > able to release 3.6.4 for ios, bb, other platforms w/o TOOLS release.
> Same
> > if we want to release 3.6.5 version of some platform later.
> >         * npm cache logic used in LIB seems to correctly handle this 
> > case and download updated platform version when it is available on npm
> >         * for --usegit option we can have 3.6 tag along with 3.6.3 
> > and
> > 3.6.4  so this will work as well
> >
> > [1]
> >
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cord
> ova/platforms.js
> >
> > Thx!
> > Sergey
> >
> > -----Original Message-----
> > From: Jesse [mailto:purplecabbage@gmail.com]
> > Sent: Saturday, September 27, 2014 2:20 AM
> > To: dev@cordova.apache.org
> > Subject: Re: Next Cordova Release
> >
> > Yes, 3.6.x branch and tag it when it is ready.
> > then they can also be cherry-picked into master, or you could commit 
> > them into master, and cherry-pick them into the 3.6.x branch ...
> >
> > @purplecabbage
> > risingj.com
> >
> > On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <cm...@gmail.com>
> wrote:
> >
> > > I'd suggest pushing the commits on to the end of the 3.6.x branch, 
> > > and then tag it 3.6.4.
> > >
> > > On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) < 
> > > v-segreb@microsoft.com> wrote:
> > >
> > > > 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?
> > >
> > >
> >
>

Re: Next Cordova Release

Posted by Ian Clelland <ic...@chromium.org>.
On Mon, Sep 29, 2014 at 2:03 PM, Steven Gill <st...@gmail.com> wrote:

> Alright lets do this!
>

Don't stop the train! :)

>
> Releasing:
> Cordova-Android 3.6.4
> Cordova-Windows 3.6.4
> Cordova-WP8 3.6.4
> Cordova-Browser 3.6.0
>
> Cordova-Lib 0.21.14
> Cordova-JS 3.7.0
> Cordova-Plugman 0.22.11
> Cordova-CLI 3.7.0
> I think it is a good time to drop the cadVer-SemVer versioning for the CLI.
> Lets just make it SemVer but start from 3.7.0
>

+1 -- Sooner or later, that not-quite-semver is going to bite us hard.
Better to get rid of it now, I think.



>
> 1) Release issue:
>  - coho create-release-bug is supposed to be used for cadence releases. It
> won't make sense when we aren't release every platform. We will have to
> create the release issue manually. This is what we have been doing for
> tools releases for a while now.
>
> 2) Platform version files should be bumped using coho. Coho also goes in
> and changes the version script output for many of the platforms (all except
> windows ones last I saw)
>
> 3) I like this idea. I personally think we should test it thoroughly before
> we push it live though. Not sure what problems might arise. If people feel
> confident with releasing this change and have tested it, I won't stand in
> the way of it being released.
>

Same here -- patch releases should be for bug fixes with no compatibility
issues, so as long as we test well, then "3.6.latest" is a better policy
than "3.6.4 exactly", I'd say.

Ian


>
> I recently merged in my Indy platform release work. I want to take this
> release to go through the process and fix any problems that come up. You
> can see the doc at
>
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
> .
> Sergey, I can work with you on this or, if you don't mind, I can take over
> from here.
>
> -Steve
>
>
> On Mon, Sep 29, 2014 at 2:45 AM, Sergey Grebnov (Akvelon) <
> v-segreb@microsoft.com> wrote:
>
> > Hi, here are release branches:
> >
> > https://github.com/apache/cordova-cli/tree/rb_3.6.4-0.21.14
> > https://github.com/apache/cordova-lib/tree/rb_0.21.14
> >
> > https://github.com/apache/cordova-android/tree/3.6.x
> > https://github.com/apache/cordova-windows/tree/3.6.x
> > https://github.com/apache/cordova-wp8/tree/3.6.x
> >
> > I've not updated versions and added tags due to the following
> > questions/issues:
> >
> > 1. I wanted to create release issue to use while updating version files
> > but it is not possible since we don't have 3.6.4 version in JIRA. Could
> > someone create it?
> >     λ coho create-release-bug --version=3.6.4
> >    Cannot find version ID number in JIRA related to "root" version
> string:
> > 3.6.4
> >
> > 2. Is it ok to bump platform version files manually? - I see we mixed
> coho
> > and manual edits during 3.6.3 release.
> >
> > 3. What do you think if we change depending platform versions in
> > platforms.js [1] to 3.6 (or 3.6.x) instead of 3.6.3/4?  This way we will
> be
> > able to release 3.6.4 for ios, bb, other platforms w/o TOOLS release.
> Same
> > if we want to release 3.6.5 version of some platform later.
> >         * npm cache logic used in LIB seems to correctly handle this case
> > and download updated platform version when it is available on npm
> >         * for --usegit option we can have 3.6 tag along with 3.6.3 and
> > 3.6.4  so this will work as well
> >
> > [1]
> >
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platforms.js
> >
> > Thx!
> > Sergey
> >
> > -----Original Message-----
> > From: Jesse [mailto:purplecabbage@gmail.com]
> > Sent: Saturday, September 27, 2014 2:20 AM
> > To: dev@cordova.apache.org
> > Subject: Re: Next Cordova Release
> >
> > Yes, 3.6.x branch and tag it when it is ready.
> > then they can also be cherry-picked into master, or you could commit them
> > into master, and cherry-pick them into the 3.6.x branch ...
> >
> > @purplecabbage
> > risingj.com
> >
> > On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <cm...@gmail.com>
> wrote:
> >
> > > I'd suggest pushing the commits on to the end of the 3.6.x branch, and
> > > then tag it 3.6.4.
> > >
> > > On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) <
> > > v-segreb@microsoft.com> wrote:
> > >
> > > > 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?
> > >
> > >
> >
>

Re: Next Cordova Release

Posted by Steven Gill <st...@gmail.com>.
Alright lets do this!

Releasing:
Cordova-Android 3.6.4
Cordova-Windows 3.6.4
Cordova-WP8 3.6.4
Cordova-Browser 3.6.0

Cordova-Lib 0.21.14
Cordova-JS 3.7.0
Cordova-Plugman 0.22.11
Cordova-CLI 3.7.0
I think it is a good time to drop the cadVer-SemVer versioning for the CLI.
Lets just make it SemVer but start from 3.7.0

1) Release issue:
 - coho create-release-bug is supposed to be used for cadence releases. It
won't make sense when we aren't release every platform. We will have to
create the release issue manually. This is what we have been doing for
tools releases for a while now.

2) Platform version files should be bumped using coho. Coho also goes in
and changes the version script output for many of the platforms (all except
windows ones last I saw)

3) I like this idea. I personally think we should test it thoroughly before
we push it live though. Not sure what problems might arise. If people feel
confident with releasing this change and have tested it, I won't stand in
the way of it being released.

I recently merged in my Indy platform release work. I want to take this
release to go through the process and fix any problems that come up. You
can see the doc at
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md.
Sergey, I can work with you on this or, if you don't mind, I can take over
from here.

-Steve


On Mon, Sep 29, 2014 at 2:45 AM, Sergey Grebnov (Akvelon) <
v-segreb@microsoft.com> wrote:

> Hi, here are release branches:
>
> https://github.com/apache/cordova-cli/tree/rb_3.6.4-0.21.14
> https://github.com/apache/cordova-lib/tree/rb_0.21.14
>
> https://github.com/apache/cordova-android/tree/3.6.x
> https://github.com/apache/cordova-windows/tree/3.6.x
> https://github.com/apache/cordova-wp8/tree/3.6.x
>
> I've not updated versions and added tags due to the following
> questions/issues:
>
> 1. I wanted to create release issue to use while updating version files
> but it is not possible since we don't have 3.6.4 version in JIRA. Could
> someone create it?
>     λ coho create-release-bug --version=3.6.4
>    Cannot find version ID number in JIRA related to "root" version string:
> 3.6.4
>
> 2. Is it ok to bump platform version files manually? - I see we mixed coho
> and manual edits during 3.6.3 release.
>
> 3. What do you think if we change depending platform versions in
> platforms.js [1] to 3.6 (or 3.6.x) instead of 3.6.3/4?  This way we will be
> able to release 3.6.4 for ios, bb, other platforms w/o TOOLS release. Same
> if we want to release 3.6.5 version of some platform later.
>         * npm cache logic used in LIB seems to correctly handle this case
> and download updated platform version when it is available on npm
>         * for --usegit option we can have 3.6 tag along with 3.6.3 and
> 3.6.4  so this will work as well
>
> [1]
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platforms.js
>
> Thx!
> Sergey
>
> -----Original Message-----
> From: Jesse [mailto:purplecabbage@gmail.com]
> Sent: Saturday, September 27, 2014 2:20 AM
> To: dev@cordova.apache.org
> Subject: Re: Next Cordova Release
>
> Yes, 3.6.x branch and tag it when it is ready.
> then they can also be cherry-picked into master, or you could commit them
> into master, and cherry-pick them into the 3.6.x branch ...
>
> @purplecabbage
> risingj.com
>
> On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > I'd suggest pushing the commits on to the end of the 3.6.x branch, and
> > then tag it 3.6.4.
> >
> > On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) <
> > v-segreb@microsoft.com> wrote:
> >
> > > 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?
> >
> >
>

RE: Next Cordova Release

Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
Hi, here are release branches:

https://github.com/apache/cordova-cli/tree/rb_3.6.4-0.21.14 
https://github.com/apache/cordova-lib/tree/rb_0.21.14

https://github.com/apache/cordova-android/tree/3.6.x 
https://github.com/apache/cordova-windows/tree/3.6.x
https://github.com/apache/cordova-wp8/tree/3.6.x

I've not updated versions and added tags due to the following questions/issues:

1. I wanted to create release issue to use while updating version files but it is not possible since we don't have 3.6.4 version in JIRA. Could someone create it?
    λ coho create-release-bug --version=3.6.4  
   Cannot find version ID number in JIRA related to "root" version string: 3.6.4

2. Is it ok to bump platform version files manually? - I see we mixed coho and manual edits during 3.6.3 release.

3. What do you think if we change depending platform versions in platforms.js [1] to 3.6 (or 3.6.x) instead of 3.6.3/4?  This way we will be able to release 3.6.4 for ios, bb, other platforms w/o TOOLS release. Same if we want to release 3.6.5 version of some platform later.
	* npm cache logic used in LIB seems to correctly handle this case and download updated platform version when it is available on npm
	* for --usegit option we can have 3.6 tag along with 3.6.3 and 3.6.4  so this will work as well

[1] https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platforms.js 

Thx!
Sergey

-----Original Message-----
From: Jesse [mailto:purplecabbage@gmail.com] 
Sent: Saturday, September 27, 2014 2:20 AM
To: dev@cordova.apache.org
Subject: Re: Next Cordova Release

Yes, 3.6.x branch and tag it when it is ready.
then they can also be cherry-picked into master, or you could commit them into master, and cherry-pick them into the 3.6.x branch ...

@purplecabbage
risingj.com

On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <cm...@gmail.com> wrote:

> I'd suggest pushing the commits on to the end of the 3.6.x branch, and 
> then tag it 3.6.4.
>
> On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) < 
> v-segreb@microsoft.com> wrote:
>
> > 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?
>
>

Re: Next Cordova Release

Posted by Jesse <pu...@gmail.com>.
Yes, 3.6.x branch and tag it when it is ready.
then they can also be cherry-picked into master, or you could commit them
into master, and cherry-pick them into the 3.6.x branch ...

@purplecabbage
risingj.com

On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <cm...@gmail.com> wrote:

> I'd suggest pushing the commits on to the end of the 3.6.x branch, and
> then tag it 3.6.4.
>
> On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) <
> v-segreb@microsoft.com> wrote:
>
> > 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?
>
>

Re: Next Cordova Release

Posted by Marcel Kinard <cm...@gmail.com>.
I'd suggest pushing the commits on to the end of the 3.6.x branch, and then tag it 3.6.4.

On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) <v-...@microsoft.com> wrote:

> 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?


RE: Next Cordova Release

Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
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:csantana23@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-segreb@microsoft.com> wrote:

> That helped, thx a lot, Steven!
>
> -----Original Message-----
> From: Steven Gill [mailto:stevengill97@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-segreb@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:csantana23@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 <stevengill97@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.archana@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) < panarasi@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
> > <csantana23@gmail.com <javascript:;>>
> >
>



--
Carlos Santana
<cs...@gmail.com>

Re: Next Cordova Release

Posted by Carlos Santana <cs...@gmail.com>.
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-segreb@microsoft.com> wrote:

> That helped, thx a lot, Steven!
>
> -----Original Message-----
> From: Steven Gill [mailto:stevengill97@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-segreb@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:csantana23@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 <stevengill97@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.archana@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) < panarasi@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
> > <csantana23@gmail.com <javascript:;>>
> >
>



-- 
Carlos Santana
<cs...@gmail.com>

RE: Next Cordova Release

Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
That helped, thx a lot, Steven!

-----Original Message-----
From: Steven Gill [mailto:stevengill97@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-segreb@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:csantana23@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 <stevengill97@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.archana@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) < panarasi@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
> <csantana23@gmail.com <javascript:;>>
>

Re: Next Cordova Release

Posted by Steven Gill <st...@gmail.com>.
I think it depends on what people are working on. Not everyone needs to
work of master for cli, lib, & JS. It probably isn't a good idea to do this
automatically. Might confuse people who want to work with releases code
only or people who aren't familiar with npm link.

On Thursday, September 25, 2014, Marcel Kinard <cm...@gmail.com> wrote:

> There are now more than a couple npm-links which should be set up. Would
> it make sense to automatically do that for both the dependent and dependee
> in coho-repo-update or coho-repo-clone or createmobilespec.js or elsewhere?
>
> On Sep 25, 2014, at 12:34 PM, Steven Gill <stevengill97@gmail.com
> <javascript:;>> wrote:
>
> > 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-segreb@microsoft.com <javascript:;>> 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:csantana23@gmail.com <javascript:;>
> <javascript:;>]
> >> Sent: Thursday, September 25, 2014 1:26 AM
> >> To: dev@cordova.apache.org <javascript:;> <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 <stevengill97@gmail.com
> <javascript:;>
> >> <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.archana@gmail.com <javascript:;> <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) < panarasi@microsoft.com <javascript:;> <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
> >> <csantana23@gmail.com <javascript:;> <javascript:;>>
> >>
>
>

Re: Next Cordova Release

Posted by Marcel Kinard <cm...@gmail.com>.
There are now more than a couple npm-links which should be set up. Would it make sense to automatically do that for both the dependent and dependee in coho-repo-update or coho-repo-clone or createmobilespec.js or elsewhere?

On Sep 25, 2014, at 12:34 PM, Steven Gill <st...@gmail.com> wrote:

> 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-segreb@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:csantana23@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 <stevengill97@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.archana@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) < panarasi@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
>> <csantana23@gmail.com <javascript:;>>
>> 


Re: Next Cordova Release

Posted by Steven Gill <st...@gmail.com>.
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-segreb@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:csantana23@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 <stevengill97@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.archana@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) < panarasi@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
> <csantana23@gmail.com <javascript:;>>
>

RE: Next Cordova Release

Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
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:csantana23@gmail.com] 
Sent: Thursday, September 25, 2014 1:26 AM
To: dev@cordova.apache.org
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 <st...@gmail.com> 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 
> <na...@gmail.com>
> 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) < panarasi@microsoft.com> 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
<cs...@gmail.com>

Re: Next Cordova Release

Posted by Carlos Santana <cs...@gmail.com>.
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 <st...@gmail.com> 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 <na...@gmail.com>
> 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) <
> > panarasi@microsoft.com> 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
<cs...@gmail.com>

Re: Next Cordova Release

Posted by Steven Gill <st...@gmail.com>.
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 <na...@gmail.com>
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) <
> panarasi@microsoft.com> 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).
> >
>

Re: Next Cordova Release

Posted by Archana Naik <na...@gmail.com>.
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) <
panarasi@microsoft.com> 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).
>