cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Clelland <iclell...@chromium.org>
Subject Re: Next Cordova Release
Date Mon, 29 Sep 2014 18:15:53 GMT
On Mon, Sep 29, 2014 at 2:03 PM, Steven Gill <stevengill97@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 <cmarcelk@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?
> > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message