cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Grebnov (Akvelon)" <>
Subject RE: Next Cordova Release
Date Mon, 29 Sep 2014 09:45:01 GMT
Hi, here are release branches:

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



-----Original Message-----
From: Jesse [] 
Sent: Saturday, September 27, 2014 2:20 AM
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 ...


On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard <> 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) < 
>> 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?
View raw message