You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@chromium.org> on 2013/09/09 16:42:58 UTC
3.1 Release
I think it's time to get the ball rolling on this. It'll be the first
release post-3.0, so will likely have a few bumps to work through.
How about:
Friday 13th - Create release branches & tag RC of all repos
Monday 16th - Draft Release Blog Post (digest of changelogs)
Thurs 19th - Tag 3.1.0 for all repos
Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
The main feature of this release will be plugman-registry I think. That
said, since CLI / Plugman aren't tied to cadence releases, I think it's
just cordova-docs that is relevant.
Re: 3.1 Release
Posted by Brian LeRoux <b...@brian.io>.
Sounds good
On Sep 9, 2013 7:50 AM, "Andrew Grieve" <ag...@chromium.org> wrote:
> I think it's time to get the ball rolling on this. It'll be the first
> release post-3.0, so will likely have a few bumps to work through.
>
> How about:
>
> Friday 13th - Create release branches & tag RC of all repos
> Monday 16th - Draft Release Blog Post (digest of changelogs)
> Thurs 19th - Tag 3.1.0 for all repos
> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>
> The main feature of this release will be plugman-registry I think. That
> said, since CLI / Plugman aren't tied to cadence releases, I think it's
> just cordova-docs that is relevant.
>
Re: 3.1 Release
Posted by Jesse <pu...@gmail.com>.
I am working for Win8 inclusion.
Can we skip the dash in the version number? 3.2.0-dev is problematic for
now, I can create issues to support it, but I expect at least some things
will break. 3.2.0dev works great for me.
@purplecabbage
risingj.com
On Mon, Sep 16, 2013 at 1:09 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Also - FYI - I updated the coho command today to update the VERSION file on
> repo master branches to be "3.2.0-dev".
>
>
> On Mon, Sep 16, 2013 at 4:08 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Release Bug:
> > https://issues.apache.org/jira/browse/CB-4830
> >
> > I've done the first task (tagging JS).
> >
> > The release bug may not have all of the platforms that it should. Wasn't
> > sure if win 8 or ffos should be in the list. If so, please add them :)
> >
> >
> > On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage <purplecabbage@gmail.com
> >wrote:
> >
> >> I'm still on a couple loose ends on windows8 and wp7/8. I'll tag
> shortly.
> >>
> >> Sent from my iPhone
> >>
> >> > On Sep 16, 2013, at 12:06 PM, Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >> >
> >> > Looks like no one volunteered for release master, so I'll do so for
> this
> >> > one.
> >> >
> >> > First up is creating the release bug and branching JS / Spec. I'll get
> >> on
> >> > it and report back! :)
> >> >
> >> >
> >> >> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com>
> wrote:
> >> >>
> >> >> So, what's happening with this release?
> >> >>
> >> >> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <
> agrieve@chromium.org>
> >> >> wrote:
> >> >>> Sure! New plan:
> >> >>>
> >> >>> Monday 16th - Create release branches & tag RC of all repos
> >> >>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> >> >>> Monday 20th - Tag 3.1.0 for all repos
> >> >>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >> >>>
> >> >>> While we're at it, anyone want to volunteer to be Release Master? (
> >> >>> https://wiki.apache.org/cordova/ReleaseMaster)
> >> >>>
> >> >>> Any of our Component Leads want to not be?
> >> >>> Android: Joe
> >> >>> BlackBerry: Lorin
> >> >>> CLI: Braden
> >> >>> JS: Andrew
> >> >>> Docs: Michael B
> >> >>> iOS: Shaz
> >> >>> Windows: Jesse
> >> >>> OSX: Shaz
> >> >>>
> >> >>>
> >> >>>
> >> >>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com>
> >> wrote:
> >> >>>>
> >> >>>> Can we move this so it happens on Mondays instead of Fridays.
> >> >>>> Releasing on a Friday is never a good idea, especially since we're
> >> >>>> going to be MIA for those two Fridays with internal stuff at the
> >> >>>> Vancouver Adobe office).
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com>
> >> >> wrote:
> >> >>>>> Andrew, thanks for kicking it off. Also should note inclusion of
> >> iOS
> >> >> 7
> >> >>>> support.
> >> >>>>> -James Jong
> >> >>>>>
> >> >>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
> >> >> wrote:
> >> >>>>>
> >> >>>>>> I think it's time to get the ball rolling on this. It'll be the
> >> first
> >> >>>>>> release post-3.0, so will likely have a few bumps to work
> through.
> >> >>>>>>
> >> >>>>>> How about:
> >> >>>>>>
> >> >>>>>> Friday 13th - Create release branches & tag RC of all repos
> >> >>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
> >> >>>>>> Thurs 19th - Tag 3.1.0 for all repos
> >> >>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >> >>>>>>
> >> >>>>>> The main feature of this release will be plugman-registry I
> think.
> >> >> That
> >> >>>>>> said, since CLI / Plugman aren't tied to cadence releases, I
> think
> >> >> it's
> >> >>>>>> just cordova-docs that is relevant.
> >> >>
> >>
> >
> >
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
I'm totally fine with doing the branch cutting. Doing the actual testing is
the time intensive part though.
On Tue, Sep 17, 2013 at 12:00 PM, Joe Bowser <bo...@gmail.com> wrote:
> Andrew, why don't you tag all the RC1 yourself, since you're the only
> one who can.
>
>
> On Tue, Sep 17, 2013 at 7:11 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
> > Jesse - The "-" in there is needed for the version to be
> semver-compatible.
> > There was some work done to support the missing -, but I think it's still
> > the case that without it plugins that have <engine> tags that require
> > "cordova-win8 >= 3.1.0" might fail to parse your version without the -.
> > Probably not something that needs to be fixed right away though since
> it'll
> > still work fine for released versions.
> >
> > Joe - Yep, obviously I'd prefer you to try and fix coho, but certainly
> it's
> > use isn't a requirement. Do be careful not to miss steps though. That's
> the
> > goal of the tool.
> >
> > I ran it on cordova-android, and it did find that you missed a few
> things:
> >
> > ./cordova-coho/coho prepare-release-branch -r android --version 3.1.0-rc1
> > ... SNIP ...
> > ==== All work complete. 3 commits were made locally.
> > ==== To review changes:
> > ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-status -r
> android
> > -b master -b 3.1.x
> > ==== To push changes:
> > ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-push -r android
> -b
> > master -b 3.1.x
> > ==== To revert all local commits:
> > ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-reset -r android
> > -b master -b 3.1.x
> >
> >
> > /Users/agrieve/git/cordova/cordova-coho/coho repo-status -r android -b
> > master -b 3.1.x
> >
> > ====
> > ====
> > ====
> > ==== cordova-android on branch master (vs origin/master): Commits exist.
> > ==== a9423f3 Set VERSION to 3.2.0-dev (via coho)
> > ==== c4bdd92 Update JS snapshot to version 3.1.0-rc1 (via coho)
> > ==== cordova-android on branch 3.1.x (vs origin/3.1.x): Commits exist.
> > ==== 47ac311 Set VERSION to 3.1.0-rc1 (via coho)
> > ====
> > ==== Diff (truncated) for cordova-android on branch master (vs
> > origin/master):
> > ==== diff --git a/VERSION b/VERSION
> > ==== index 9001211..df4a767 100644
> > ==== --- a/VERSION
> > ==== +++ b/VERSION
> > ==== @@ -1 +1 @@
> > ==== -dev
> > ==== \ No newline at end of file
> > ==== +3.2.0-dev
> > ==== diff --git a/bin/templates/cordova/version
> > b/bin/templates/cordova/version
> > ==== index 04e734c..36c3388 100755
> > ==== --- a/bin/templates/cordova/version
> > ==== +++ b/bin/templates/cordova/version
> > ==== @@ -20,6 +20,6 @@
> > ==== */
> > ====
> > ==== // Coho updates this line:
> > ==== -var VERSION = '3.1.0-dev';
> > ==== +var VERSION = "3.2.0-dev";
> > ====
> > ==== console.log(VERSION);
> > ==== diff --git a/framework/assets/www/cordova.js
> > b/framework/assets/www/cordova.js
> > ==== index f798e7a..5f0ac0d 100644
> > ==== --- a/framework/assets/www/cordova.js
> > ==== +++ b/framework/assets/www/cordova.js
> > ==== @@ -1,5 +1,5 @@
> > ==== // Platform: android
> > ==== -// 3.0.0rc1-1-g1965a39
> > ==== +// 3.1.0-rc1-0-g0d70465
> > ==== /*
> > ==== Licensed to the Apache Software Foundation (ASF) under one
> > ====
> > ==== Diff (truncated) for cordova-android on branch 3.1.x (vs
> origin/3.1.x):
> > ==== diff --git a/bin/templates/cordova/version
> > b/bin/templates/cordova/version
> > ==== index 04e734c..42bab55 100755
> > ==== --- a/bin/templates/cordova/version
> > ==== +++ b/bin/templates/cordova/version
> > ==== @@ -20,6 +20,6 @@
> > ==== */
> > ====
> > ==== // Coho updates this line:
> > ==== -var VERSION = '3.1.0-dev';
> > ==== +var VERSION = "3.1.0-rc1";
> > ====
> > ==== console.log(VERSION);
> > ==== diff --git a/framework/src/org/apache/cordova/CordovaWebView.java
> > b/framework/src/org/apache/cordova/CordovaWebView.java
> > ==== index beb41ac..b1fc5e8 100755
> > ==== --- a/framework/src/org/apache/cordova/CordovaWebView.java
> > ==== +++ b/framework/src/org/apache/cordova/CordovaWebView.java
> > ==== @@ -61,7 +61,7 @@ public class CordovaWebView extends WebView {
> > ====
> > ==== public static final String TAG = "CordovaWebView";
> > ====
> > ==== - public static final String CORDOVA_VERSION = "3.1.0-dev";
> > ==== + public static final String CORDOVA_VERSION = "3.1.0-rc1";
> > ====
> > ==== private ArrayList<Integer> keyDownCodes = new
> > ArrayList<Integer>();
> > ==== private ArrayList<Integer> keyUpCodes = new
> ArrayList<Integer>();
> > ====
> > ====
> >
> >
> >
> > As for CHANGELOG.md, I was hoping we could start one (following suite
> from
> > cordova-ios's RELEASENOTES.md). It makes writing "what's new" blog posts
> > easier, and also helps to identify what needs extra testing. I actually
> > didn't mean to change the name from RELEASENOTES, so I'll add the file
> > update the instructions to use this name.
> >
> >
> >
> >
> >
> >
> > On Mon, Sep 16, 2013 at 5:02 PM, Joe Bowser <bo...@gmail.com> wrote:
> >
> >> You set the version on the 3.1.x branch to 3.2.x-dev.
> >>
> >> I tried following the steps on the wiki, and coho still fails horribly
> >> on this end. I'm going to keep tagging the old fashioned way with
> >> git. We should try and keep use of coho only for what we have
> >> problems with (managing multiple plugin repositories), and keep it out
> >> of the parts that we don't (tagging releases, testing, etc).
> >>
> >>
> >>
> >> On Mon, Sep 16, 2013 at 1:09 PM, Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >> > Also - FYI - I updated the coho command today to update the VERSION
> file
> >> on
> >> > repo master branches to be "3.2.0-dev".
> >> >
> >> >
> >> > On Mon, Sep 16, 2013 at 4:08 PM, Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >> >
> >> >> Release Bug:
> >> >> https://issues.apache.org/jira/browse/CB-4830
> >> >>
> >> >> I've done the first task (tagging JS).
> >> >>
> >> >> The release bug may not have all of the platforms that it should.
> Wasn't
> >> >> sure if win 8 or ffos should be in the list. If so, please add them
> :)
> >> >>
> >> >>
> >> >> On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage <
> purplecabbage@gmail.com
> >> >wrote:
> >> >>
> >> >>> I'm still on a couple loose ends on windows8 and wp7/8. I'll tag
> >> shortly.
> >> >>>
> >> >>> Sent from my iPhone
> >> >>>
> >> >>> > On Sep 16, 2013, at 12:06 PM, Andrew Grieve <agrieve@chromium.org
> >
> >> >>> wrote:
> >> >>> >
> >> >>> > Looks like no one volunteered for release master, so I'll do so
> for
> >> this
> >> >>> > one.
> >> >>> >
> >> >>> > First up is creating the release bug and branching JS / Spec. I'll
> >> get
> >> >>> on
> >> >>> > it and report back! :)
> >> >>> >
> >> >>> >
> >> >>> >> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com>
> >> wrote:
> >> >>> >>
> >> >>> >> So, what's happening with this release?
> >> >>> >>
> >> >>> >> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <
> >> agrieve@chromium.org>
> >> >>> >> wrote:
> >> >>> >>> Sure! New plan:
> >> >>> >>>
> >> >>> >>> Monday 16th - Create release branches & tag RC of all repos
> >> >>> >>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> >> >>> >>> Monday 20th - Tag 3.1.0 for all repos
> >> >>> >>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >> >>> >>>
> >> >>> >>> While we're at it, anyone want to volunteer to be Release
> Master? (
> >> >>> >>> https://wiki.apache.org/cordova/ReleaseMaster)
> >> >>> >>>
> >> >>> >>> Any of our Component Leads want to not be?
> >> >>> >>> Android: Joe
> >> >>> >>> BlackBerry: Lorin
> >> >>> >>> CLI: Braden
> >> >>> >>> JS: Andrew
> >> >>> >>> Docs: Michael B
> >> >>> >>> iOS: Shaz
> >> >>> >>> Windows: Jesse
> >> >>> >>> OSX: Shaz
> >> >>> >>>
> >> >>> >>>
> >> >>> >>>
> >> >>> >>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bowserj@gmail.com
> >
> >> >>> wrote:
> >> >>> >>>>
> >> >>> >>>> Can we move this so it happens on Mondays instead of Fridays.
> >> >>> >>>> Releasing on a Friday is never a good idea, especially since
> we're
> >> >>> >>>> going to be MIA for those two Fridays with internal stuff at
> the
> >> >>> >>>> Vancouver Adobe office).
> >> >>> >>>>
> >> >>> >>>>
> >> >>> >>>>
> >> >>> >>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <
> wjamesjong@gmail.com>
> >> >>> >> wrote:
> >> >>> >>>>> Andrew, thanks for kicking it off. Also should note
> inclusion of
> >> >>> iOS
> >> >>> >> 7
> >> >>> >>>> support.
> >> >>> >>>>> -James Jong
> >> >>> >>>>>
> >> >>> >>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> agrieve@chromium.org
> >> >
> >> >>> >> wrote:
> >> >>> >>>>>
> >> >>> >>>>>> I think it's time to get the ball rolling on this. It'll be
> the
> >> >>> first
> >> >>> >>>>>> release post-3.0, so will likely have a few bumps to work
> >> through.
> >> >>> >>>>>>
> >> >>> >>>>>> How about:
> >> >>> >>>>>>
> >> >>> >>>>>> Friday 13th - Create release branches & tag RC of all repos
> >> >>> >>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
> >> >>> >>>>>> Thurs 19th - Tag 3.1.0 for all repos
> >> >>> >>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >> >>> >>>>>>
> >> >>> >>>>>> The main feature of this release will be plugman-registry I
> >> think.
> >> >>> >> That
> >> >>> >>>>>> said, since CLI / Plugman aren't tied to cadence releases, I
> >> think
> >> >>> >> it's
> >> >>> >>>>>> just cordova-docs that is relevant.
> >> >>> >>
> >> >>>
> >> >>
> >> >>
> >>
>
Re: 3.1 Release
Posted by Joe Bowser <bo...@gmail.com>.
Andrew, why don't you tag all the RC1 yourself, since you're the only
one who can.
On Tue, Sep 17, 2013 at 7:11 AM, Andrew Grieve <ag...@chromium.org> wrote:
> Jesse - The "-" in there is needed for the version to be semver-compatible.
> There was some work done to support the missing -, but I think it's still
> the case that without it plugins that have <engine> tags that require
> "cordova-win8 >= 3.1.0" might fail to parse your version without the -.
> Probably not something that needs to be fixed right away though since it'll
> still work fine for released versions.
>
> Joe - Yep, obviously I'd prefer you to try and fix coho, but certainly it's
> use isn't a requirement. Do be careful not to miss steps though. That's the
> goal of the tool.
>
> I ran it on cordova-android, and it did find that you missed a few things:
>
> ./cordova-coho/coho prepare-release-branch -r android --version 3.1.0-rc1
> ... SNIP ...
> ==== All work complete. 3 commits were made locally.
> ==== To review changes:
> ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-status -r android
> -b master -b 3.1.x
> ==== To push changes:
> ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-push -r android -b
> master -b 3.1.x
> ==== To revert all local commits:
> ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-reset -r android
> -b master -b 3.1.x
>
>
> /Users/agrieve/git/cordova/cordova-coho/coho repo-status -r android -b
> master -b 3.1.x
>
> ====
> ====
> ====
> ==== cordova-android on branch master (vs origin/master): Commits exist.
> ==== a9423f3 Set VERSION to 3.2.0-dev (via coho)
> ==== c4bdd92 Update JS snapshot to version 3.1.0-rc1 (via coho)
> ==== cordova-android on branch 3.1.x (vs origin/3.1.x): Commits exist.
> ==== 47ac311 Set VERSION to 3.1.0-rc1 (via coho)
> ====
> ==== Diff (truncated) for cordova-android on branch master (vs
> origin/master):
> ==== diff --git a/VERSION b/VERSION
> ==== index 9001211..df4a767 100644
> ==== --- a/VERSION
> ==== +++ b/VERSION
> ==== @@ -1 +1 @@
> ==== -dev
> ==== \ No newline at end of file
> ==== +3.2.0-dev
> ==== diff --git a/bin/templates/cordova/version
> b/bin/templates/cordova/version
> ==== index 04e734c..36c3388 100755
> ==== --- a/bin/templates/cordova/version
> ==== +++ b/bin/templates/cordova/version
> ==== @@ -20,6 +20,6 @@
> ==== */
> ====
> ==== // Coho updates this line:
> ==== -var VERSION = '3.1.0-dev';
> ==== +var VERSION = "3.2.0-dev";
> ====
> ==== console.log(VERSION);
> ==== diff --git a/framework/assets/www/cordova.js
> b/framework/assets/www/cordova.js
> ==== index f798e7a..5f0ac0d 100644
> ==== --- a/framework/assets/www/cordova.js
> ==== +++ b/framework/assets/www/cordova.js
> ==== @@ -1,5 +1,5 @@
> ==== // Platform: android
> ==== -// 3.0.0rc1-1-g1965a39
> ==== +// 3.1.0-rc1-0-g0d70465
> ==== /*
> ==== Licensed to the Apache Software Foundation (ASF) under one
> ====
> ==== Diff (truncated) for cordova-android on branch 3.1.x (vs origin/3.1.x):
> ==== diff --git a/bin/templates/cordova/version
> b/bin/templates/cordova/version
> ==== index 04e734c..42bab55 100755
> ==== --- a/bin/templates/cordova/version
> ==== +++ b/bin/templates/cordova/version
> ==== @@ -20,6 +20,6 @@
> ==== */
> ====
> ==== // Coho updates this line:
> ==== -var VERSION = '3.1.0-dev';
> ==== +var VERSION = "3.1.0-rc1";
> ====
> ==== console.log(VERSION);
> ==== diff --git a/framework/src/org/apache/cordova/CordovaWebView.java
> b/framework/src/org/apache/cordova/CordovaWebView.java
> ==== index beb41ac..b1fc5e8 100755
> ==== --- a/framework/src/org/apache/cordova/CordovaWebView.java
> ==== +++ b/framework/src/org/apache/cordova/CordovaWebView.java
> ==== @@ -61,7 +61,7 @@ public class CordovaWebView extends WebView {
> ====
> ==== public static final String TAG = "CordovaWebView";
> ====
> ==== - public static final String CORDOVA_VERSION = "3.1.0-dev";
> ==== + public static final String CORDOVA_VERSION = "3.1.0-rc1";
> ====
> ==== private ArrayList<Integer> keyDownCodes = new
> ArrayList<Integer>();
> ==== private ArrayList<Integer> keyUpCodes = new ArrayList<Integer>();
> ====
> ====
>
>
>
> As for CHANGELOG.md, I was hoping we could start one (following suite from
> cordova-ios's RELEASENOTES.md). It makes writing "what's new" blog posts
> easier, and also helps to identify what needs extra testing. I actually
> didn't mean to change the name from RELEASENOTES, so I'll add the file
> update the instructions to use this name.
>
>
>
>
>
>
> On Mon, Sep 16, 2013 at 5:02 PM, Joe Bowser <bo...@gmail.com> wrote:
>
>> You set the version on the 3.1.x branch to 3.2.x-dev.
>>
>> I tried following the steps on the wiki, and coho still fails horribly
>> on this end. I'm going to keep tagging the old fashioned way with
>> git. We should try and keep use of coho only for what we have
>> problems with (managing multiple plugin repositories), and keep it out
>> of the parts that we don't (tagging releases, testing, etc).
>>
>>
>>
>> On Mon, Sep 16, 2013 at 1:09 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>> > Also - FYI - I updated the coho command today to update the VERSION file
>> on
>> > repo master branches to be "3.2.0-dev".
>> >
>> >
>> > On Mon, Sep 16, 2013 at 4:08 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>> >
>> >> Release Bug:
>> >> https://issues.apache.org/jira/browse/CB-4830
>> >>
>> >> I've done the first task (tagging JS).
>> >>
>> >> The release bug may not have all of the platforms that it should. Wasn't
>> >> sure if win 8 or ffos should be in the list. If so, please add them :)
>> >>
>> >>
>> >> On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage <purplecabbage@gmail.com
>> >wrote:
>> >>
>> >>> I'm still on a couple loose ends on windows8 and wp7/8. I'll tag
>> shortly.
>> >>>
>> >>> Sent from my iPhone
>> >>>
>> >>> > On Sep 16, 2013, at 12:06 PM, Andrew Grieve <ag...@chromium.org>
>> >>> wrote:
>> >>> >
>> >>> > Looks like no one volunteered for release master, so I'll do so for
>> this
>> >>> > one.
>> >>> >
>> >>> > First up is creating the release bug and branching JS / Spec. I'll
>> get
>> >>> on
>> >>> > it and report back! :)
>> >>> >
>> >>> >
>> >>> >> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com>
>> wrote:
>> >>> >>
>> >>> >> So, what's happening with this release?
>> >>> >>
>> >>> >> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <
>> agrieve@chromium.org>
>> >>> >> wrote:
>> >>> >>> Sure! New plan:
>> >>> >>>
>> >>> >>> Monday 16th - Create release branches & tag RC of all repos
>> >>> >>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>> >>> >>> Monday 20th - Tag 3.1.0 for all repos
>> >>> >>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>> >>>
>> >>> >>> While we're at it, anyone want to volunteer to be Release Master? (
>> >>> >>> https://wiki.apache.org/cordova/ReleaseMaster)
>> >>> >>>
>> >>> >>> Any of our Component Leads want to not be?
>> >>> >>> Android: Joe
>> >>> >>> BlackBerry: Lorin
>> >>> >>> CLI: Braden
>> >>> >>> JS: Andrew
>> >>> >>> Docs: Michael B
>> >>> >>> iOS: Shaz
>> >>> >>> Windows: Jesse
>> >>> >>> OSX: Shaz
>> >>> >>>
>> >>> >>>
>> >>> >>>
>> >>> >>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com>
>> >>> wrote:
>> >>> >>>>
>> >>> >>>> Can we move this so it happens on Mondays instead of Fridays.
>> >>> >>>> Releasing on a Friday is never a good idea, especially since we're
>> >>> >>>> going to be MIA for those two Fridays with internal stuff at the
>> >>> >>>> Vancouver Adobe office).
>> >>> >>>>
>> >>> >>>>
>> >>> >>>>
>> >>> >>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com>
>> >>> >> wrote:
>> >>> >>>>> Andrew, thanks for kicking it off. Also should note inclusion of
>> >>> iOS
>> >>> >> 7
>> >>> >>>> support.
>> >>> >>>>> -James Jong
>> >>> >>>>>
>> >>> >>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <agrieve@chromium.org
>> >
>> >>> >> wrote:
>> >>> >>>>>
>> >>> >>>>>> I think it's time to get the ball rolling on this. It'll be the
>> >>> first
>> >>> >>>>>> release post-3.0, so will likely have a few bumps to work
>> through.
>> >>> >>>>>>
>> >>> >>>>>> How about:
>> >>> >>>>>>
>> >>> >>>>>> Friday 13th - Create release branches & tag RC of all repos
>> >>> >>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
>> >>> >>>>>> Thurs 19th - Tag 3.1.0 for all repos
>> >>> >>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>> >>>>>>
>> >>> >>>>>> The main feature of this release will be plugman-registry I
>> think.
>> >>> >> That
>> >>> >>>>>> said, since CLI / Plugman aren't tied to cadence releases, I
>> think
>> >>> >> it's
>> >>> >>>>>> just cordova-docs that is relevant.
>> >>> >>
>> >>>
>> >>
>> >>
>>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
In other news, I had to re-tag the JS because the build label was wrong.
You can actually see it in the previous email's output. It was
"3.1.0-rc1-0-g0d70465"
it should be "3.1.0-rc1". I've fixed it and re-tagged the JS.
On Tue, Sep 17, 2013 at 10:11 AM, Andrew Grieve <ag...@chromium.org>wrote:
> Jesse - The "-" in there is needed for the version to be
> semver-compatible. There was some work done to support the missing -, but I
> think it's still the case that without it plugins that have <engine> tags
> that require "cordova-win8 >= 3.1.0" might fail to parse your version
> without the -. Probably not something that needs to be fixed right away
> though since it'll still work fine for released versions.
>
> Joe - Yep, obviously I'd prefer you to try and fix coho, but certainly
> it's use isn't a requirement. Do be careful not to miss steps though.
> That's the goal of the tool.
>
> I ran it on cordova-android, and it did find that you missed a few things:
>
> ./cordova-coho/coho prepare-release-branch -r android --version 3.1.0-rc1
> ... SNIP ...
> ==== All work complete. 3 commits were made locally.
> ==== To review changes:
> ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-status -r android
> -b master -b 3.1.x
> ==== To push changes:
> ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-push -r android
> -b master -b 3.1.x
> ==== To revert all local commits:
> ==== /Users/agrieve/git/cordova/cordova-coho/coho repo-reset -r android
> -b master -b 3.1.x
>
>
> /Users/agrieve/git/cordova/cordova-coho/coho repo-status -r android -b
> master -b 3.1.x
>
> ====
> ====
> ====
> ==== cordova-android on branch master (vs origin/master): Commits exist.
> ==== a9423f3 Set VERSION to 3.2.0-dev (via coho)
> ==== c4bdd92 Update JS snapshot to version 3.1.0-rc1 (via coho)
> ==== cordova-android on branch 3.1.x (vs origin/3.1.x): Commits exist.
> ==== 47ac311 Set VERSION to 3.1.0-rc1 (via coho)
> ====
> ==== Diff (truncated) for cordova-android on branch master (vs
> origin/master):
> ==== diff --git a/VERSION b/VERSION
> ==== index 9001211..df4a767 100644
> ==== --- a/VERSION
> ==== +++ b/VERSION
> ==== @@ -1 +1 @@
> ==== -dev
> ==== \ No newline at end of file
> ==== +3.2.0-dev
> ==== diff --git a/bin/templates/cordova/version
> b/bin/templates/cordova/version
> ==== index 04e734c..36c3388 100755
> ==== --- a/bin/templates/cordova/version
> ==== +++ b/bin/templates/cordova/version
> ==== @@ -20,6 +20,6 @@
> ==== */
> ====
> ==== // Coho updates this line:
> ==== -var VERSION = '3.1.0-dev';
> ==== +var VERSION = "3.2.0-dev";
> ====
> ==== console.log(VERSION);
> ==== diff --git a/framework/assets/www/cordova.js
> b/framework/assets/www/cordova.js
> ==== index f798e7a..5f0ac0d 100644
> ==== --- a/framework/assets/www/cordova.js
> ==== +++ b/framework/assets/www/cordova.js
> ==== @@ -1,5 +1,5 @@
> ==== // Platform: android
> ==== -// 3.0.0rc1-1-g1965a39
> ==== +// 3.1.0-rc1-0-g0d70465
> ==== /*
> ==== Licensed to the Apache Software Foundation (ASF) under one
> ====
> ==== Diff (truncated) for cordova-android on branch 3.1.x (vs
> origin/3.1.x):
> ==== diff --git a/bin/templates/cordova/version
> b/bin/templates/cordova/version
> ==== index 04e734c..42bab55 100755
> ==== --- a/bin/templates/cordova/version
> ==== +++ b/bin/templates/cordova/version
> ==== @@ -20,6 +20,6 @@
> ==== */
> ====
> ==== // Coho updates this line:
> ==== -var VERSION = '3.1.0-dev';
> ==== +var VERSION = "3.1.0-rc1";
> ====
> ==== console.log(VERSION);
> ==== diff --git a/framework/src/org/apache/cordova/CordovaWebView.java
> b/framework/src/org/apache/cordova/CordovaWebView.java
> ==== index beb41ac..b1fc5e8 100755
> ==== --- a/framework/src/org/apache/cordova/CordovaWebView.java
> ==== +++ b/framework/src/org/apache/cordova/CordovaWebView.java
> ==== @@ -61,7 +61,7 @@ public class CordovaWebView extends WebView {
> ====
> ==== public static final String TAG = "CordovaWebView";
> ====
> ==== - public static final String CORDOVA_VERSION = "3.1.0-dev";
> ==== + public static final String CORDOVA_VERSION = "3.1.0-rc1";
> ====
> ==== private ArrayList<Integer> keyDownCodes = new
> ArrayList<Integer>();
> ==== private ArrayList<Integer> keyUpCodes = new ArrayList<Integer>();
> ====
> ====
>
>
>
> As for CHANGELOG.md, I was hoping we could start one (following suite from
> cordova-ios's RELEASENOTES.md). It makes writing "what's new" blog posts
> easier, and also helps to identify what needs extra testing. I actually
> didn't mean to change the name from RELEASENOTES, so I'll add the file
> update the instructions to use this name.
>
>
>
>
>
>
> On Mon, Sep 16, 2013 at 5:02 PM, Joe Bowser <bo...@gmail.com> wrote:
>
>> You set the version on the 3.1.x branch to 3.2.x-dev.
>>
>> I tried following the steps on the wiki, and coho still fails horribly
>> on this end. I'm going to keep tagging the old fashioned way with
>> git. We should try and keep use of coho only for what we have
>> problems with (managing multiple plugin repositories), and keep it out
>> of the parts that we don't (tagging releases, testing, etc).
>>
>>
>>
>> On Mon, Sep 16, 2013 at 1:09 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>> > Also - FYI - I updated the coho command today to update the VERSION
>> file on
>> > repo master branches to be "3.2.0-dev".
>> >
>> >
>> > On Mon, Sep 16, 2013 at 4:08 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>> >
>> >> Release Bug:
>> >> https://issues.apache.org/jira/browse/CB-4830
>> >>
>> >> I've done the first task (tagging JS).
>> >>
>> >> The release bug may not have all of the platforms that it should.
>> Wasn't
>> >> sure if win 8 or ffos should be in the list. If so, please add them :)
>> >>
>> >>
>> >> On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage <
>> purplecabbage@gmail.com>wrote:
>> >>
>> >>> I'm still on a couple loose ends on windows8 and wp7/8. I'll tag
>> shortly.
>> >>>
>> >>> Sent from my iPhone
>> >>>
>> >>> > On Sep 16, 2013, at 12:06 PM, Andrew Grieve <ag...@chromium.org>
>> >>> wrote:
>> >>> >
>> >>> > Looks like no one volunteered for release master, so I'll do so for
>> this
>> >>> > one.
>> >>> >
>> >>> > First up is creating the release bug and branching JS / Spec. I'll
>> get
>> >>> on
>> >>> > it and report back! :)
>> >>> >
>> >>> >
>> >>> >> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com>
>> wrote:
>> >>> >>
>> >>> >> So, what's happening with this release?
>> >>> >>
>> >>> >> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <
>> agrieve@chromium.org>
>> >>> >> wrote:
>> >>> >>> Sure! New plan:
>> >>> >>>
>> >>> >>> Monday 16th - Create release branches & tag RC of all repos
>> >>> >>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>> >>> >>> Monday 20th - Tag 3.1.0 for all repos
>> >>> >>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>> >>>
>> >>> >>> While we're at it, anyone want to volunteer to be Release Master?
>> (
>> >>> >>> https://wiki.apache.org/cordova/ReleaseMaster)
>> >>> >>>
>> >>> >>> Any of our Component Leads want to not be?
>> >>> >>> Android: Joe
>> >>> >>> BlackBerry: Lorin
>> >>> >>> CLI: Braden
>> >>> >>> JS: Andrew
>> >>> >>> Docs: Michael B
>> >>> >>> iOS: Shaz
>> >>> >>> Windows: Jesse
>> >>> >>> OSX: Shaz
>> >>> >>>
>> >>> >>>
>> >>> >>>
>> >>> >>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com>
>> >>> wrote:
>> >>> >>>>
>> >>> >>>> Can we move this so it happens on Mondays instead of Fridays.
>> >>> >>>> Releasing on a Friday is never a good idea, especially since
>> we're
>> >>> >>>> going to be MIA for those two Fridays with internal stuff at the
>> >>> >>>> Vancouver Adobe office).
>> >>> >>>>
>> >>> >>>>
>> >>> >>>>
>> >>> >>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wjamesjong@gmail.com
>> >
>> >>> >> wrote:
>> >>> >>>>> Andrew, thanks for kicking it off. Also should note inclusion
>> of
>> >>> iOS
>> >>> >> 7
>> >>> >>>> support.
>> >>> >>>>> -James Jong
>> >>> >>>>>
>> >>> >>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
>> agrieve@chromium.org>
>> >>> >> wrote:
>> >>> >>>>>
>> >>> >>>>>> I think it's time to get the ball rolling on this. It'll be the
>> >>> first
>> >>> >>>>>> release post-3.0, so will likely have a few bumps to work
>> through.
>> >>> >>>>>>
>> >>> >>>>>> How about:
>> >>> >>>>>>
>> >>> >>>>>> Friday 13th - Create release branches & tag RC of all repos
>> >>> >>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
>> >>> >>>>>> Thurs 19th - Tag 3.1.0 for all repos
>> >>> >>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>> >>>>>>
>> >>> >>>>>> The main feature of this release will be plugman-registry I
>> think.
>> >>> >> That
>> >>> >>>>>> said, since CLI / Plugman aren't tied to cadence releases, I
>> think
>> >>> >> it's
>> >>> >>>>>> just cordova-docs that is relevant.
>> >>> >>
>> >>>
>> >>
>> >>
>>
>
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Jesse - The "-" in there is needed for the version to be semver-compatible.
There was some work done to support the missing -, but I think it's still
the case that without it plugins that have <engine> tags that require
"cordova-win8 >= 3.1.0" might fail to parse your version without the -.
Probably not something that needs to be fixed right away though since it'll
still work fine for released versions.
Joe - Yep, obviously I'd prefer you to try and fix coho, but certainly it's
use isn't a requirement. Do be careful not to miss steps though. That's the
goal of the tool.
I ran it on cordova-android, and it did find that you missed a few things:
./cordova-coho/coho prepare-release-branch -r android --version 3.1.0-rc1
... SNIP ...
==== All work complete. 3 commits were made locally.
==== To review changes:
==== /Users/agrieve/git/cordova/cordova-coho/coho repo-status -r android
-b master -b 3.1.x
==== To push changes:
==== /Users/agrieve/git/cordova/cordova-coho/coho repo-push -r android -b
master -b 3.1.x
==== To revert all local commits:
==== /Users/agrieve/git/cordova/cordova-coho/coho repo-reset -r android
-b master -b 3.1.x
/Users/agrieve/git/cordova/cordova-coho/coho repo-status -r android -b
master -b 3.1.x
====
====
====
==== cordova-android on branch master (vs origin/master): Commits exist.
==== a9423f3 Set VERSION to 3.2.0-dev (via coho)
==== c4bdd92 Update JS snapshot to version 3.1.0-rc1 (via coho)
==== cordova-android on branch 3.1.x (vs origin/3.1.x): Commits exist.
==== 47ac311 Set VERSION to 3.1.0-rc1 (via coho)
====
==== Diff (truncated) for cordova-android on branch master (vs
origin/master):
==== diff --git a/VERSION b/VERSION
==== index 9001211..df4a767 100644
==== --- a/VERSION
==== +++ b/VERSION
==== @@ -1 +1 @@
==== -dev
==== \ No newline at end of file
==== +3.2.0-dev
==== diff --git a/bin/templates/cordova/version
b/bin/templates/cordova/version
==== index 04e734c..36c3388 100755
==== --- a/bin/templates/cordova/version
==== +++ b/bin/templates/cordova/version
==== @@ -20,6 +20,6 @@
==== */
====
==== // Coho updates this line:
==== -var VERSION = '3.1.0-dev';
==== +var VERSION = "3.2.0-dev";
====
==== console.log(VERSION);
==== diff --git a/framework/assets/www/cordova.js
b/framework/assets/www/cordova.js
==== index f798e7a..5f0ac0d 100644
==== --- a/framework/assets/www/cordova.js
==== +++ b/framework/assets/www/cordova.js
==== @@ -1,5 +1,5 @@
==== // Platform: android
==== -// 3.0.0rc1-1-g1965a39
==== +// 3.1.0-rc1-0-g0d70465
==== /*
==== Licensed to the Apache Software Foundation (ASF) under one
====
==== Diff (truncated) for cordova-android on branch 3.1.x (vs origin/3.1.x):
==== diff --git a/bin/templates/cordova/version
b/bin/templates/cordova/version
==== index 04e734c..42bab55 100755
==== --- a/bin/templates/cordova/version
==== +++ b/bin/templates/cordova/version
==== @@ -20,6 +20,6 @@
==== */
====
==== // Coho updates this line:
==== -var VERSION = '3.1.0-dev';
==== +var VERSION = "3.1.0-rc1";
====
==== console.log(VERSION);
==== diff --git a/framework/src/org/apache/cordova/CordovaWebView.java
b/framework/src/org/apache/cordova/CordovaWebView.java
==== index beb41ac..b1fc5e8 100755
==== --- a/framework/src/org/apache/cordova/CordovaWebView.java
==== +++ b/framework/src/org/apache/cordova/CordovaWebView.java
==== @@ -61,7 +61,7 @@ public class CordovaWebView extends WebView {
====
==== public static final String TAG = "CordovaWebView";
====
==== - public static final String CORDOVA_VERSION = "3.1.0-dev";
==== + public static final String CORDOVA_VERSION = "3.1.0-rc1";
====
==== private ArrayList<Integer> keyDownCodes = new
ArrayList<Integer>();
==== private ArrayList<Integer> keyUpCodes = new ArrayList<Integer>();
====
====
As for CHANGELOG.md, I was hoping we could start one (following suite from
cordova-ios's RELEASENOTES.md). It makes writing "what's new" blog posts
easier, and also helps to identify what needs extra testing. I actually
didn't mean to change the name from RELEASENOTES, so I'll add the file
update the instructions to use this name.
On Mon, Sep 16, 2013 at 5:02 PM, Joe Bowser <bo...@gmail.com> wrote:
> You set the version on the 3.1.x branch to 3.2.x-dev.
>
> I tried following the steps on the wiki, and coho still fails horribly
> on this end. I'm going to keep tagging the old fashioned way with
> git. We should try and keep use of coho only for what we have
> problems with (managing multiple plugin repositories), and keep it out
> of the parts that we don't (tagging releases, testing, etc).
>
>
>
> On Mon, Sep 16, 2013 at 1:09 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
> > Also - FYI - I updated the coho command today to update the VERSION file
> on
> > repo master branches to be "3.2.0-dev".
> >
> >
> > On Mon, Sep 16, 2013 at 4:08 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
> >
> >> Release Bug:
> >> https://issues.apache.org/jira/browse/CB-4830
> >>
> >> I've done the first task (tagging JS).
> >>
> >> The release bug may not have all of the platforms that it should. Wasn't
> >> sure if win 8 or ffos should be in the list. If so, please add them :)
> >>
> >>
> >> On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage <purplecabbage@gmail.com
> >wrote:
> >>
> >>> I'm still on a couple loose ends on windows8 and wp7/8. I'll tag
> shortly.
> >>>
> >>> Sent from my iPhone
> >>>
> >>> > On Sep 16, 2013, at 12:06 PM, Andrew Grieve <ag...@chromium.org>
> >>> wrote:
> >>> >
> >>> > Looks like no one volunteered for release master, so I'll do so for
> this
> >>> > one.
> >>> >
> >>> > First up is creating the release bug and branching JS / Spec. I'll
> get
> >>> on
> >>> > it and report back! :)
> >>> >
> >>> >
> >>> >> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com>
> wrote:
> >>> >>
> >>> >> So, what's happening with this release?
> >>> >>
> >>> >> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <
> agrieve@chromium.org>
> >>> >> wrote:
> >>> >>> Sure! New plan:
> >>> >>>
> >>> >>> Monday 16th - Create release branches & tag RC of all repos
> >>> >>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> >>> >>> Monday 20th - Tag 3.1.0 for all repos
> >>> >>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>> >>>
> >>> >>> While we're at it, anyone want to volunteer to be Release Master? (
> >>> >>> https://wiki.apache.org/cordova/ReleaseMaster)
> >>> >>>
> >>> >>> Any of our Component Leads want to not be?
> >>> >>> Android: Joe
> >>> >>> BlackBerry: Lorin
> >>> >>> CLI: Braden
> >>> >>> JS: Andrew
> >>> >>> Docs: Michael B
> >>> >>> iOS: Shaz
> >>> >>> Windows: Jesse
> >>> >>> OSX: Shaz
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com>
> >>> wrote:
> >>> >>>>
> >>> >>>> Can we move this so it happens on Mondays instead of Fridays.
> >>> >>>> Releasing on a Friday is never a good idea, especially since we're
> >>> >>>> going to be MIA for those two Fridays with internal stuff at the
> >>> >>>> Vancouver Adobe office).
> >>> >>>>
> >>> >>>>
> >>> >>>>
> >>> >>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com>
> >>> >> wrote:
> >>> >>>>> Andrew, thanks for kicking it off. Also should note inclusion of
> >>> iOS
> >>> >> 7
> >>> >>>> support.
> >>> >>>>> -James Jong
> >>> >>>>>
> >>> >>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <agrieve@chromium.org
> >
> >>> >> wrote:
> >>> >>>>>
> >>> >>>>>> I think it's time to get the ball rolling on this. It'll be the
> >>> first
> >>> >>>>>> release post-3.0, so will likely have a few bumps to work
> through.
> >>> >>>>>>
> >>> >>>>>> How about:
> >>> >>>>>>
> >>> >>>>>> Friday 13th - Create release branches & tag RC of all repos
> >>> >>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
> >>> >>>>>> Thurs 19th - Tag 3.1.0 for all repos
> >>> >>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>> >>>>>>
> >>> >>>>>> The main feature of this release will be plugman-registry I
> think.
> >>> >> That
> >>> >>>>>> said, since CLI / Plugman aren't tied to cadence releases, I
> think
> >>> >> it's
> >>> >>>>>> just cordova-docs that is relevant.
> >>> >>
> >>>
> >>
> >>
>
Re: 3.1 Release
Posted by Joe Bowser <bo...@gmail.com>.
You set the version on the 3.1.x branch to 3.2.x-dev.
I tried following the steps on the wiki, and coho still fails horribly
on this end. I'm going to keep tagging the old fashioned way with
git. We should try and keep use of coho only for what we have
problems with (managing multiple plugin repositories), and keep it out
of the parts that we don't (tagging releases, testing, etc).
On Mon, Sep 16, 2013 at 1:09 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Also - FYI - I updated the coho command today to update the VERSION file on
> repo master branches to be "3.2.0-dev".
>
>
> On Mon, Sep 16, 2013 at 4:08 PM, Andrew Grieve <ag...@chromium.org> wrote:
>
>> Release Bug:
>> https://issues.apache.org/jira/browse/CB-4830
>>
>> I've done the first task (tagging JS).
>>
>> The release bug may not have all of the platforms that it should. Wasn't
>> sure if win 8 or ffos should be in the list. If so, please add them :)
>>
>>
>> On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage <pu...@gmail.com>wrote:
>>
>>> I'm still on a couple loose ends on windows8 and wp7/8. I'll tag shortly.
>>>
>>> Sent from my iPhone
>>>
>>> > On Sep 16, 2013, at 12:06 PM, Andrew Grieve <ag...@chromium.org>
>>> wrote:
>>> >
>>> > Looks like no one volunteered for release master, so I'll do so for this
>>> > one.
>>> >
>>> > First up is creating the release bug and branching JS / Spec. I'll get
>>> on
>>> > it and report back! :)
>>> >
>>> >
>>> >> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com> wrote:
>>> >>
>>> >> So, what's happening with this release?
>>> >>
>>> >> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <ag...@chromium.org>
>>> >> wrote:
>>> >>> Sure! New plan:
>>> >>>
>>> >>> Monday 16th - Create release branches & tag RC of all repos
>>> >>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>>> >>> Monday 20th - Tag 3.1.0 for all repos
>>> >>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>> >>>
>>> >>> While we're at it, anyone want to volunteer to be Release Master? (
>>> >>> https://wiki.apache.org/cordova/ReleaseMaster)
>>> >>>
>>> >>> Any of our Component Leads want to not be?
>>> >>> Android: Joe
>>> >>> BlackBerry: Lorin
>>> >>> CLI: Braden
>>> >>> JS: Andrew
>>> >>> Docs: Michael B
>>> >>> iOS: Shaz
>>> >>> Windows: Jesse
>>> >>> OSX: Shaz
>>> >>>
>>> >>>
>>> >>>
>>> >>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com>
>>> wrote:
>>> >>>>
>>> >>>> Can we move this so it happens on Mondays instead of Fridays.
>>> >>>> Releasing on a Friday is never a good idea, especially since we're
>>> >>>> going to be MIA for those two Fridays with internal stuff at the
>>> >>>> Vancouver Adobe office).
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com>
>>> >> wrote:
>>> >>>>> Andrew, thanks for kicking it off. Also should note inclusion of
>>> iOS
>>> >> 7
>>> >>>> support.
>>> >>>>> -James Jong
>>> >>>>>
>>> >>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
>>> >> wrote:
>>> >>>>>
>>> >>>>>> I think it's time to get the ball rolling on this. It'll be the
>>> first
>>> >>>>>> release post-3.0, so will likely have a few bumps to work through.
>>> >>>>>>
>>> >>>>>> How about:
>>> >>>>>>
>>> >>>>>> Friday 13th - Create release branches & tag RC of all repos
>>> >>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
>>> >>>>>> Thurs 19th - Tag 3.1.0 for all repos
>>> >>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>> >>>>>>
>>> >>>>>> The main feature of this release will be plugman-registry I think.
>>> >> That
>>> >>>>>> said, since CLI / Plugman aren't tied to cadence releases, I think
>>> >> it's
>>> >>>>>> just cordova-docs that is relevant.
>>> >>
>>>
>>
>>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Also - FYI - I updated the coho command today to update the VERSION file on
repo master branches to be "3.2.0-dev".
On Mon, Sep 16, 2013 at 4:08 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Release Bug:
> https://issues.apache.org/jira/browse/CB-4830
>
> I've done the first task (tagging JS).
>
> The release bug may not have all of the platforms that it should. Wasn't
> sure if win 8 or ffos should be in the list. If so, please add them :)
>
>
> On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage <pu...@gmail.com>wrote:
>
>> I'm still on a couple loose ends on windows8 and wp7/8. I'll tag shortly.
>>
>> Sent from my iPhone
>>
>> > On Sep 16, 2013, at 12:06 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>> >
>> > Looks like no one volunteered for release master, so I'll do so for this
>> > one.
>> >
>> > First up is creating the release bug and branching JS / Spec. I'll get
>> on
>> > it and report back! :)
>> >
>> >
>> >> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com> wrote:
>> >>
>> >> So, what's happening with this release?
>> >>
>> >> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <ag...@chromium.org>
>> >> wrote:
>> >>> Sure! New plan:
>> >>>
>> >>> Monday 16th - Create release branches & tag RC of all repos
>> >>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>> >>> Monday 20th - Tag 3.1.0 for all repos
>> >>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>>
>> >>> While we're at it, anyone want to volunteer to be Release Master? (
>> >>> https://wiki.apache.org/cordova/ReleaseMaster)
>> >>>
>> >>> Any of our Component Leads want to not be?
>> >>> Android: Joe
>> >>> BlackBerry: Lorin
>> >>> CLI: Braden
>> >>> JS: Andrew
>> >>> Docs: Michael B
>> >>> iOS: Shaz
>> >>> Windows: Jesse
>> >>> OSX: Shaz
>> >>>
>> >>>
>> >>>
>> >>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com>
>> wrote:
>> >>>>
>> >>>> Can we move this so it happens on Mondays instead of Fridays.
>> >>>> Releasing on a Friday is never a good idea, especially since we're
>> >>>> going to be MIA for those two Fridays with internal stuff at the
>> >>>> Vancouver Adobe office).
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com>
>> >> wrote:
>> >>>>> Andrew, thanks for kicking it off. Also should note inclusion of
>> iOS
>> >> 7
>> >>>> support.
>> >>>>> -James Jong
>> >>>>>
>> >>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
>> >> wrote:
>> >>>>>
>> >>>>>> I think it's time to get the ball rolling on this. It'll be the
>> first
>> >>>>>> release post-3.0, so will likely have a few bumps to work through.
>> >>>>>>
>> >>>>>> How about:
>> >>>>>>
>> >>>>>> Friday 13th - Create release branches & tag RC of all repos
>> >>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
>> >>>>>> Thurs 19th - Tag 3.1.0 for all repos
>> >>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>>>>>
>> >>>>>> The main feature of this release will be plugman-registry I think.
>> >> That
>> >>>>>> said, since CLI / Plugman aren't tied to cadence releases, I think
>> >> it's
>> >>>>>> just cordova-docs that is relevant.
>> >>
>>
>
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Release Bug:
https://issues.apache.org/jira/browse/CB-4830
I've done the first task (tagging JS).
The release bug may not have all of the platforms that it should. Wasn't
sure if win 8 or ffos should be in the list. If so, please add them :)
On Mon, Sep 16, 2013 at 3:26 PM, purplecabbage <pu...@gmail.com>wrote:
> I'm still on a couple loose ends on windows8 and wp7/8. I'll tag shortly.
>
> Sent from my iPhone
>
> > On Sep 16, 2013, at 12:06 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
> >
> > Looks like no one volunteered for release master, so I'll do so for this
> > one.
> >
> > First up is creating the release bug and branching JS / Spec. I'll get on
> > it and report back! :)
> >
> >
> >> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com> wrote:
> >>
> >> So, what's happening with this release?
> >>
> >> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >>> Sure! New plan:
> >>>
> >>> Monday 16th - Create release branches & tag RC of all repos
> >>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> >>> Monday 20th - Tag 3.1.0 for all repos
> >>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>>
> >>> While we're at it, anyone want to volunteer to be Release Master? (
> >>> https://wiki.apache.org/cordova/ReleaseMaster)
> >>>
> >>> Any of our Component Leads want to not be?
> >>> Android: Joe
> >>> BlackBerry: Lorin
> >>> CLI: Braden
> >>> JS: Andrew
> >>> Docs: Michael B
> >>> iOS: Shaz
> >>> Windows: Jesse
> >>> OSX: Shaz
> >>>
> >>>
> >>>
> >>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com>
> wrote:
> >>>>
> >>>> Can we move this so it happens on Mondays instead of Fridays.
> >>>> Releasing on a Friday is never a good idea, especially since we're
> >>>> going to be MIA for those two Fridays with internal stuff at the
> >>>> Vancouver Adobe office).
> >>>>
> >>>>
> >>>>
> >>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com>
> >> wrote:
> >>>>> Andrew, thanks for kicking it off. Also should note inclusion of iOS
> >> 7
> >>>> support.
> >>>>> -James Jong
> >>>>>
> >>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >>>>>
> >>>>>> I think it's time to get the ball rolling on this. It'll be the
> first
> >>>>>> release post-3.0, so will likely have a few bumps to work through.
> >>>>>>
> >>>>>> How about:
> >>>>>>
> >>>>>> Friday 13th - Create release branches & tag RC of all repos
> >>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
> >>>>>> Thurs 19th - Tag 3.1.0 for all repos
> >>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>>>>>
> >>>>>> The main feature of this release will be plugman-registry I think.
> >> That
> >>>>>> said, since CLI / Plugman aren't tied to cadence releases, I think
> >> it's
> >>>>>> just cordova-docs that is relevant.
> >>
>
Re: 3.1 Release
Posted by purplecabbage <pu...@gmail.com>.
I'm still on a couple loose ends on windows8 and wp7/8. I'll tag shortly.
Sent from my iPhone
> On Sep 16, 2013, at 12:06 PM, Andrew Grieve <ag...@chromium.org> wrote:
>
> Looks like no one volunteered for release master, so I'll do so for this
> one.
>
> First up is creating the release bug and branching JS / Spec. I'll get on
> it and report back! :)
>
>
>> On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com> wrote:
>>
>> So, what's happening with this release?
>>
>> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>>> Sure! New plan:
>>>
>>> Monday 16th - Create release branches & tag RC of all repos
>>> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>>> Monday 20th - Tag 3.1.0 for all repos
>>> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>>
>>> While we're at it, anyone want to volunteer to be Release Master? (
>>> https://wiki.apache.org/cordova/ReleaseMaster)
>>>
>>> Any of our Component Leads want to not be?
>>> Android: Joe
>>> BlackBerry: Lorin
>>> CLI: Braden
>>> JS: Andrew
>>> Docs: Michael B
>>> iOS: Shaz
>>> Windows: Jesse
>>> OSX: Shaz
>>>
>>>
>>>
>>>> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com> wrote:
>>>>
>>>> Can we move this so it happens on Mondays instead of Fridays.
>>>> Releasing on a Friday is never a good idea, especially since we're
>>>> going to be MIA for those two Fridays with internal stuff at the
>>>> Vancouver Adobe office).
>>>>
>>>>
>>>>
>>>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com>
>> wrote:
>>>>> Andrew, thanks for kicking it off. Also should note inclusion of iOS
>> 7
>>>> support.
>>>>> -James Jong
>>>>>
>>>>> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>>>>>
>>>>>> I think it's time to get the ball rolling on this. It'll be the first
>>>>>> release post-3.0, so will likely have a few bumps to work through.
>>>>>>
>>>>>> How about:
>>>>>>
>>>>>> Friday 13th - Create release branches & tag RC of all repos
>>>>>> Monday 16th - Draft Release Blog Post (digest of changelogs)
>>>>>> Thurs 19th - Tag 3.1.0 for all repos
>>>>>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>>>>>
>>>>>> The main feature of this release will be plugman-registry I think.
>> That
>>>>>> said, since CLI / Plugman aren't tied to cadence releases, I think
>> it's
>>>>>> just cordova-docs that is relevant.
>>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Looks like no one volunteered for release master, so I'll do so for this
one.
First up is creating the release bug and branching JS / Spec. I'll get on
it and report back! :)
On Mon, Sep 16, 2013 at 2:57 PM, Joe Bowser <bo...@gmail.com> wrote:
> So, what's happening with this release?
>
> On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
> > Sure! New plan:
> >
> > Monday 16th - Create release branches & tag RC of all repos
> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> > Monday 20th - Tag 3.1.0 for all repos
> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >
> > While we're at it, anyone want to volunteer to be Release Master? (
> > https://wiki.apache.org/cordova/ReleaseMaster)
> >
> > Any of our Component Leads want to not be?
> > Android: Joe
> > BlackBerry: Lorin
> > CLI: Braden
> > JS: Andrew
> > Docs: Michael B
> > iOS: Shaz
> > Windows: Jesse
> > OSX: Shaz
> >
> >
> >
> > On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com> wrote:
> >
> >> Can we move this so it happens on Mondays instead of Fridays.
> >> Releasing on a Friday is never a good idea, especially since we're
> >> going to be MIA for those two Fridays with internal stuff at the
> >> Vancouver Adobe office).
> >>
> >>
> >>
> >> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com>
> wrote:
> >> > Andrew, thanks for kicking it off. Also should note inclusion of iOS
> 7
> >> support.
> >> > -James Jong
> >> >
> >> > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
> >> >
> >> >> I think it's time to get the ball rolling on this. It'll be the first
> >> >> release post-3.0, so will likely have a few bumps to work through.
> >> >>
> >> >> How about:
> >> >>
> >> >> Friday 13th - Create release branches & tag RC of all repos
> >> >> Monday 16th - Draft Release Blog Post (digest of changelogs)
> >> >> Thurs 19th - Tag 3.1.0 for all repos
> >> >> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >> >>
> >> >> The main feature of this release will be plugman-registry I think.
> That
> >> >> said, since CLI / Plugman aren't tied to cadence releases, I think
> it's
> >> >> just cordova-docs that is relevant.
> >> >
> >>
>
Re: 3.1 Release
Posted by Joe Bowser <bo...@gmail.com>.
So, what's happening with this release?
On Tue, Sep 10, 2013 at 12:20 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Sure! New plan:
>
> Monday 16th - Create release branches & tag RC of all repos
> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> Monday 20th - Tag 3.1.0 for all repos
> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>
> While we're at it, anyone want to volunteer to be Release Master? (
> https://wiki.apache.org/cordova/ReleaseMaster)
>
> Any of our Component Leads want to not be?
> Android: Joe
> BlackBerry: Lorin
> CLI: Braden
> JS: Andrew
> Docs: Michael B
> iOS: Shaz
> Windows: Jesse
> OSX: Shaz
>
>
>
> On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com> wrote:
>
>> Can we move this so it happens on Mondays instead of Fridays.
>> Releasing on a Friday is never a good idea, especially since we're
>> going to be MIA for those two Fridays with internal stuff at the
>> Vancouver Adobe office).
>>
>>
>>
>> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com> wrote:
>> > Andrew, thanks for kicking it off. Also should note inclusion of iOS 7
>> support.
>> > -James Jong
>> >
>> > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org> wrote:
>> >
>> >> I think it's time to get the ball rolling on this. It'll be the first
>> >> release post-3.0, so will likely have a few bumps to work through.
>> >>
>> >> How about:
>> >>
>> >> Friday 13th - Create release branches & tag RC of all repos
>> >> Monday 16th - Draft Release Blog Post (digest of changelogs)
>> >> Thurs 19th - Tag 3.1.0 for all repos
>> >> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>
>> >> The main feature of this release will be plugman-registry I think. That
>> >> said, since CLI / Plugman aren't tied to cadence releases, I think it's
>> >> just cordova-docs that is relevant.
>> >
>>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Sure! New plan:
Monday 16th - Create release branches & tag RC of all repos
Tuesday 17th - Draft Release Blog Post (digest of changelogs)
Monday 20th - Tag 3.1.0 for all repos
Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
While we're at it, anyone want to volunteer to be Release Master? (
https://wiki.apache.org/cordova/ReleaseMaster)
Any of our Component Leads want to not be?
Android: Joe
BlackBerry: Lorin
CLI: Braden
JS: Andrew
Docs: Michael B
iOS: Shaz
Windows: Jesse
OSX: Shaz
On Tue, Sep 10, 2013 at 2:33 PM, Joe Bowser <bo...@gmail.com> wrote:
> Can we move this so it happens on Mondays instead of Fridays.
> Releasing on a Friday is never a good idea, especially since we're
> going to be MIA for those two Fridays with internal stuff at the
> Vancouver Adobe office).
>
>
>
> On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com> wrote:
> > Andrew, thanks for kicking it off. Also should note inclusion of iOS 7
> support.
> > -James Jong
> >
> > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org> wrote:
> >
> >> I think it's time to get the ball rolling on this. It'll be the first
> >> release post-3.0, so will likely have a few bumps to work through.
> >>
> >> How about:
> >>
> >> Friday 13th - Create release branches & tag RC of all repos
> >> Monday 16th - Draft Release Blog Post (digest of changelogs)
> >> Thurs 19th - Tag 3.1.0 for all repos
> >> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>
> >> The main feature of this release will be plugman-registry I think. That
> >> said, since CLI / Plugman aren't tied to cadence releases, I think it's
> >> just cordova-docs that is relevant.
> >
>
Re: 3.1 Release
Posted by Joe Bowser <bo...@gmail.com>.
Can we move this so it happens on Mondays instead of Fridays.
Releasing on a Friday is never a good idea, especially since we're
going to be MIA for those two Fridays with internal stuff at the
Vancouver Adobe office).
On Mon, Sep 9, 2013 at 8:10 AM, James Jong <wj...@gmail.com> wrote:
> Andrew, thanks for kicking it off. Also should note inclusion of iOS 7 support.
> -James Jong
>
> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org> wrote:
>
>> I think it's time to get the ball rolling on this. It'll be the first
>> release post-3.0, so will likely have a few bumps to work through.
>>
>> How about:
>>
>> Friday 13th - Create release branches & tag RC of all repos
>> Monday 16th - Draft Release Blog Post (digest of changelogs)
>> Thurs 19th - Tag 3.1.0 for all repos
>> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>
>> The main feature of this release will be plugman-registry I think. That
>> said, since CLI / Plugman aren't tied to cadence releases, I think it's
>> just cordova-docs that is relevant.
>
Re: 3.1 Release
Posted by James Jong <wj...@gmail.com>.
Andrew, thanks for kicking it off. Also should note inclusion of iOS 7 support.
-James Jong
On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org> wrote:
> I think it's time to get the ball rolling on this. It'll be the first
> release post-3.0, so will likely have a few bumps to work through.
>
> How about:
>
> Friday 13th - Create release branches & tag RC of all repos
> Monday 16th - Draft Release Blog Post (digest of changelogs)
> Thurs 19th - Tag 3.1.0 for all repos
> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>
> The main feature of this release will be plugman-registry I think. That
> said, since CLI / Plugman aren't tied to cadence releases, I think it's
> just cordova-docs that is relevant.
Re: 3.1 Release
Posted by Anis KADRI <an...@gmail.com>.
Sweet! Thanks Steve! Hopefully I didn't break anything :-S
On Thu, Sep 26, 2013 at 8:24 AM, Steven Gill <st...@gmail.com> wrote:
> I have merged the dev branches into master on my machine and tagged all of
> the plugins. I am planning on merging this into master tomorrow if no one
> has any issues.
>
> I will also send a review request for the plugin release blog once I finish
> it tomorrow.
>
> Tracking everything at https://issues.apache.org/jira/browse/CB-4915
>
> -Steve
>
>
> On Wed, Sep 25, 2013 at 10:26 AM, Steven Gill <st...@gmail.com>wrote:
>
>> Michael,
>>
>> Good point. I think the issue arrises if some of our users keep using 3.0,
>> install plugins using the git url (master branch) and then try to remove
>> the plugins using the 3.0 documentation. When the master branch gets
>> updated, it won't have core in the ID. This will make the remove
>> instructions incorrect.
>>
>> An upgrade guide/blog post actually sounds like the best way to handle
>> this issue.
>>
>> I am going to pick up where Anis left of and aim to do a plugin release
>> later this afternoon
>>
>> -Steve
>>
>>
>> On Wed, Sep 25, 2013 at 6:45 AM, Carlos Santana <cs...@gmail.com>wrote:
>>
>>> It could be a doc or or blog post, I would suggest blog post for plugins
>>> for more details about dealing with registry since those have a faster
>>> pace
>>>
>>> --Carlos
>>>
>>>
>>>
>>> On Wed, Sep 25, 2013 at 9:43 AM, Carlos Santana <csantana23@gmail.com
>>> >wrote:
>>>
>>> > Would suggest we document a simple workflow document "Upgrade Guide
>>> > Cordova CLI/PlugMan 3.0 to 3.1"
>>> > Same way that we do for the platforms on going over the details in a
>>> > single document.
>>> >
>>> > --Carlos
>>> >
>>> >
>>> > On Wed, Sep 25, 2013 at 9:38 AM, Michal Mocny <mm...@chromium.org>
>>> wrote:
>>> >
>>> >> I think the 3.0 instructions of removing the old plugin with the old ID
>>> >> remain correct even after we update the registry. Thats because when
>>> >> removing plugins from a workspace you use the ID of whats locally
>>> >> installed.
>>> >>
>>> >> So, to upgrade, users would have the use the 3.0 uninstall guide and
>>> the
>>> >> 3.1 install guide.. I think?
>>> >>
>>> >> -Michal
>>> >>
>>> >>
>>> >> On Wed, Sep 25, 2013 at 7:31 AM, Anis KADRI <an...@gmail.com>
>>> wrote:
>>> >>
>>> >> > That's a good summary. I am going to be fixing the reference problem
>>> >> > shortly and merge them back to the `dev` branch. Not sure if all of
>>> >> > Jesse's changes have made it to the `dev` branch yet.
>>> >> >
>>> >> > The `edge` docs have already been updated (see CB-4493)
>>> >> >
>>> >> > The `3.0` docs will have to be updated once we merge `dev` back to
>>> >> > `master` (which I hope we will before we release 3.1).
>>> >> >
>>> >> >
>>> >> > On Wed, Sep 25, 2013 at 1:25 AM, Steven Gill <stevengill97@gmail.com
>>> >
>>> >> > wrote:
>>> >> > > I realize why Anis decided to do a new branch (3.1.0) because he
>>> >> didn't
>>> >> > > want to mess up dev/master. Before we release 3.1.0 we need to do a
>>> >> > plugin
>>> >> > > release based off of
>>> >> > http://wiki.apache.org/cordova/StepsForPluginRelease.
>>> >> > > Jesse has changes for the plugins that he has pushed to dev now
>>> based
>>> >> on
>>> >> > > this email thread. He needs these changes to be in the next plugin
>>> >> > release
>>> >> > > we are doing for the 3.1.0 release.
>>> >> > >
>>> >> > > If I am understanding this correctly, removing core from ID was not
>>> >> > > something we want in master due to 3.0.0 support. But this ID
>>> change
>>> >> > should
>>> >> > > have been done on dev before creating the 3.1.0 branch. The 3.0.0
>>> docs
>>> >> > get
>>> >> > > users to install plugins using the git url. The problem is that the
>>> >> 3.0.0
>>> >> > > docs instruct our users to use the ID for plugin removal. Obviously
>>> >> if we
>>> >> > > change the ID, the remove documentation for 3.0.0 would be wrong.
>>> >> > >
>>> >> > > We have two options here as far as I can tell
>>> >> > >
>>> >> > > 1) Leave master alone for the next month or two and give people
>>> time
>>> >> to
>>> >> > > migrate to 3.1
>>> >> > > 2) Update the 3.0 documentation to refer to updated id, Push the
>>> >> updated
>>> >> > ID
>>> >> > > to dev then master.
>>> >> > >
>>> >> > > Things that need to be done
>>> >> > > - Fix incorrect references to the old ID (last comment on
>>> >> > > https://issues.apache.org/jira/browse/CB-4889)
>>> >> > > - Merge these changes into dev (they really should be on dev if
>>> that
>>> >> is
>>> >> > > where we all the work done)
>>> >> > > - Follow steps on
>>> >> http://wiki.apache.org/cordova/StepsForPluginReleaseand
>>> >> > > publish these plugins on our registry. This should include Jesse's
>>> >> work
>>> >> > as
>>> >> > > well.
>>> >> > > - Update edge docs to refer to registry for plugin installation
>>> (not
>>> >> > sure
>>> >> > > if this has been done)
>>> >> > > - Update 3.0.0 documentation if we decide option 2 from above is
>>> the
>>> >> way
>>> >> > > to go
>>> >> > > - Tag docs 3.1.0-rc1
>>> >> > >
>>> >> > > I volunteer to take the lead on getting the plugins released +
>>> tested
>>> >> > > (supposed to be today according to Andrew's timeline) for tomorrow
>>> >> > > afternoon. I can get to the docs after that.
>>> >> > >
>>> >> > > Before I dive into this full steam, any feedback on above?
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > > On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny <mmocny@chromium.org
>>> >
>>> >> > wrote:
>>> >> > >
>>> >> > >> Just to be super duper clear: the reason to work on 'dev' branch
>>> of
>>> >> > plugins
>>> >> > >> is not some process decision we are imposing, its a direct
>>> >> requirement
>>> >> > >> imposed on us by the limitations of our tools (specifically, the
>>> >> state
>>> >> > of
>>> >> > >> the registry as it was with 3.0 launch).
>>> >> > >>
>>> >> > >> We discussed this in-depth just a week ago (Read "About plugins in
>>> >> > 3.1"),
>>> >> > >> and I think several other times over the last month, if you would
>>> >> like
>>> >> > to
>>> >> > >> read up on the details look there.
>>> >> > >>
>>> >> > >> No one likes the situation, we've been making headway into fixing
>>> it
>>> >> > ever
>>> >> > >> since we discovered the problem, and it can be resolved as soon as
>>> >> users
>>> >> > >> upgrade from 3.0 (maybe that means we can switch after 3.1
>>> release,
>>> >> > maybe
>>> >> > >> that means we wait for some 3-months deprecation time, not sure).
>>> >> > >>
>>> >> > >> -Michal
>>> >> > >>
>>> >> > >>
>>> >> > >> On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <
>>> >> > braden@chromium.org
>>> >> > >> >wrote:
>>> >> > >>
>>> >> > >> > I agree with Joe that developing on anything other than master
>>> >> sucks.
>>> >> > But
>>> >> > >> > unfortunately, our hands are tied in the near term because the
>>> >> > registry
>>> >> > >> > doesn't know to fetch plugins from anywhere else. Also it makes
>>> >> life
>>> >> > >> easier
>>> >> > >> > for being who are installing plugins from git URLs.
>>> >> > >> >
>>> >> > >> > I think we eventually want to get to a world where 99% of plugin
>>> >> > installs
>>> >> > >> > are happening from the registry, the registry knows how to fetch
>>> >> tags,
>>> >> > >> and
>>> >> > >> > people who are using git URLs directly know what they're doing
>>> and
>>> >> > want
>>> >> > >> the
>>> >> > >> > dev version. (Also you can specify branches with #gitref in the
>>> >> URL,
>>> >> > so
>>> >> > >> > there's flexibility there.) But we're not there yet.
>>> >> > >> >
>>> >> > >> > Braden
>>> >> > >> >
>>> >> > >> >
>>> >> > >> > On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com>
>>> >> wrote:
>>> >> > >> >
>>> >> > >> > > Yes, let's get this cleared up - confused myself.
>>> >> > >> > >
>>> >> > >> > >
>>> >> > >> > > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <
>>> >> anis.kadri@gmail.com>
>>> >> > >> > wrote:
>>> >> > >> > >
>>> >> > >> > > > 3.1.0 is coincidental and it's temporary for this release
>>> >> because
>>> >> > I
>>> >> > >> > > > wasn't sure where to get the code from and didn't want to
>>> >> > compromise
>>> >> > >> > > > master or dev. I could have called it something else.
>>> >> > >> > > >
>>> >> > >> > > > Jesse, I'd advise you to commit to dev. Everything will be
>>> >> merged
>>> >> > to
>>> >> > >> > > > master eventually.
>>> >> > >> > > >
>>> >> > >> > > > So to re-iterate the process: right now it's "dev -> master"
>>> >> and
>>> >> > >> > > > eventually it will be "master -> (independant) plugin
>>> version".
>>> >> > >> > > > amarite?
>>> >> > >> > > >
>>> >> > >> > > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <
>>> >> bowserj@gmail.com>
>>> >> > >> > wrote:
>>> >> > >> > > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <
>>> >> > >> agrieve@chromium.org
>>> >> > >> > >
>>> >> > >> > > > wrote:
>>> >> > >> > > > >> Plugins are not tagged nor branched along with platforms.
>>> >> They
>>> >> > are
>>> >> > >> > > > releases
>>> >> > >> > > > >> completely independently.
>>> >> > >> > > > >>
>>> >> > >> > > > >> Commit to the "dev" branch always.
>>> >> > >> > > > >
>>> >> > >> > > > > AND FOREVER!!!!!11!!eleventyone!!!
>>> >> > >> > > > >
>>> >> > >> > > > > Seriously, can't we have a stable branch instead? Having
>>> the
>>> >> dev
>>> >> > >> > > > > branch for dev on plugins and having master for dev on
>>> >> > platforms is
>>> >> > >> > > > > stupid and makes it harder to do work.
>>> >> > >> > > >
>>> >> > >> > >
>>> >> > >> >
>>> >> > >>
>>> >> >
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Carlos Santana
>>> > <cs...@gmail.com>
>>> >
>>>
>>>
>>>
>>> --
>>> Carlos Santana
>>> <cs...@gmail.com>
>>>
>>
>>
Re: 3.1 Release
Posted by Steven Gill <st...@gmail.com>.
I have merged the dev branches into master on my machine and tagged all of
the plugins. I am planning on merging this into master tomorrow if no one
has any issues.
I will also send a review request for the plugin release blog once I finish
it tomorrow.
Tracking everything at https://issues.apache.org/jira/browse/CB-4915
-Steve
On Wed, Sep 25, 2013 at 10:26 AM, Steven Gill <st...@gmail.com>wrote:
> Michael,
>
> Good point. I think the issue arrises if some of our users keep using 3.0,
> install plugins using the git url (master branch) and then try to remove
> the plugins using the 3.0 documentation. When the master branch gets
> updated, it won't have core in the ID. This will make the remove
> instructions incorrect.
>
> An upgrade guide/blog post actually sounds like the best way to handle
> this issue.
>
> I am going to pick up where Anis left of and aim to do a plugin release
> later this afternoon
>
> -Steve
>
>
> On Wed, Sep 25, 2013 at 6:45 AM, Carlos Santana <cs...@gmail.com>wrote:
>
>> It could be a doc or or blog post, I would suggest blog post for plugins
>> for more details about dealing with registry since those have a faster
>> pace
>>
>> --Carlos
>>
>>
>>
>> On Wed, Sep 25, 2013 at 9:43 AM, Carlos Santana <csantana23@gmail.com
>> >wrote:
>>
>> > Would suggest we document a simple workflow document "Upgrade Guide
>> > Cordova CLI/PlugMan 3.0 to 3.1"
>> > Same way that we do for the platforms on going over the details in a
>> > single document.
>> >
>> > --Carlos
>> >
>> >
>> > On Wed, Sep 25, 2013 at 9:38 AM, Michal Mocny <mm...@chromium.org>
>> wrote:
>> >
>> >> I think the 3.0 instructions of removing the old plugin with the old ID
>> >> remain correct even after we update the registry. Thats because when
>> >> removing plugins from a workspace you use the ID of whats locally
>> >> installed.
>> >>
>> >> So, to upgrade, users would have the use the 3.0 uninstall guide and
>> the
>> >> 3.1 install guide.. I think?
>> >>
>> >> -Michal
>> >>
>> >>
>> >> On Wed, Sep 25, 2013 at 7:31 AM, Anis KADRI <an...@gmail.com>
>> wrote:
>> >>
>> >> > That's a good summary. I am going to be fixing the reference problem
>> >> > shortly and merge them back to the `dev` branch. Not sure if all of
>> >> > Jesse's changes have made it to the `dev` branch yet.
>> >> >
>> >> > The `edge` docs have already been updated (see CB-4493)
>> >> >
>> >> > The `3.0` docs will have to be updated once we merge `dev` back to
>> >> > `master` (which I hope we will before we release 3.1).
>> >> >
>> >> >
>> >> > On Wed, Sep 25, 2013 at 1:25 AM, Steven Gill <stevengill97@gmail.com
>> >
>> >> > wrote:
>> >> > > I realize why Anis decided to do a new branch (3.1.0) because he
>> >> didn't
>> >> > > want to mess up dev/master. Before we release 3.1.0 we need to do a
>> >> > plugin
>> >> > > release based off of
>> >> > http://wiki.apache.org/cordova/StepsForPluginRelease.
>> >> > > Jesse has changes for the plugins that he has pushed to dev now
>> based
>> >> on
>> >> > > this email thread. He needs these changes to be in the next plugin
>> >> > release
>> >> > > we are doing for the 3.1.0 release.
>> >> > >
>> >> > > If I am understanding this correctly, removing core from ID was not
>> >> > > something we want in master due to 3.0.0 support. But this ID
>> change
>> >> > should
>> >> > > have been done on dev before creating the 3.1.0 branch. The 3.0.0
>> docs
>> >> > get
>> >> > > users to install plugins using the git url. The problem is that the
>> >> 3.0.0
>> >> > > docs instruct our users to use the ID for plugin removal. Obviously
>> >> if we
>> >> > > change the ID, the remove documentation for 3.0.0 would be wrong.
>> >> > >
>> >> > > We have two options here as far as I can tell
>> >> > >
>> >> > > 1) Leave master alone for the next month or two and give people
>> time
>> >> to
>> >> > > migrate to 3.1
>> >> > > 2) Update the 3.0 documentation to refer to updated id, Push the
>> >> updated
>> >> > ID
>> >> > > to dev then master.
>> >> > >
>> >> > > Things that need to be done
>> >> > > - Fix incorrect references to the old ID (last comment on
>> >> > > https://issues.apache.org/jira/browse/CB-4889)
>> >> > > - Merge these changes into dev (they really should be on dev if
>> that
>> >> is
>> >> > > where we all the work done)
>> >> > > - Follow steps on
>> >> http://wiki.apache.org/cordova/StepsForPluginReleaseand
>> >> > > publish these plugins on our registry. This should include Jesse's
>> >> work
>> >> > as
>> >> > > well.
>> >> > > - Update edge docs to refer to registry for plugin installation
>> (not
>> >> > sure
>> >> > > if this has been done)
>> >> > > - Update 3.0.0 documentation if we decide option 2 from above is
>> the
>> >> way
>> >> > > to go
>> >> > > - Tag docs 3.1.0-rc1
>> >> > >
>> >> > > I volunteer to take the lead on getting the plugins released +
>> tested
>> >> > > (supposed to be today according to Andrew's timeline) for tomorrow
>> >> > > afternoon. I can get to the docs after that.
>> >> > >
>> >> > > Before I dive into this full steam, any feedback on above?
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>> >> > > On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny <mmocny@chromium.org
>> >
>> >> > wrote:
>> >> > >
>> >> > >> Just to be super duper clear: the reason to work on 'dev' branch
>> of
>> >> > plugins
>> >> > >> is not some process decision we are imposing, its a direct
>> >> requirement
>> >> > >> imposed on us by the limitations of our tools (specifically, the
>> >> state
>> >> > of
>> >> > >> the registry as it was with 3.0 launch).
>> >> > >>
>> >> > >> We discussed this in-depth just a week ago (Read "About plugins in
>> >> > 3.1"),
>> >> > >> and I think several other times over the last month, if you would
>> >> like
>> >> > to
>> >> > >> read up on the details look there.
>> >> > >>
>> >> > >> No one likes the situation, we've been making headway into fixing
>> it
>> >> > ever
>> >> > >> since we discovered the problem, and it can be resolved as soon as
>> >> users
>> >> > >> upgrade from 3.0 (maybe that means we can switch after 3.1
>> release,
>> >> > maybe
>> >> > >> that means we wait for some 3-months deprecation time, not sure).
>> >> > >>
>> >> > >> -Michal
>> >> > >>
>> >> > >>
>> >> > >> On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <
>> >> > braden@chromium.org
>> >> > >> >wrote:
>> >> > >>
>> >> > >> > I agree with Joe that developing on anything other than master
>> >> sucks.
>> >> > But
>> >> > >> > unfortunately, our hands are tied in the near term because the
>> >> > registry
>> >> > >> > doesn't know to fetch plugins from anywhere else. Also it makes
>> >> life
>> >> > >> easier
>> >> > >> > for being who are installing plugins from git URLs.
>> >> > >> >
>> >> > >> > I think we eventually want to get to a world where 99% of plugin
>> >> > installs
>> >> > >> > are happening from the registry, the registry knows how to fetch
>> >> tags,
>> >> > >> and
>> >> > >> > people who are using git URLs directly know what they're doing
>> and
>> >> > want
>> >> > >> the
>> >> > >> > dev version. (Also you can specify branches with #gitref in the
>> >> URL,
>> >> > so
>> >> > >> > there's flexibility there.) But we're not there yet.
>> >> > >> >
>> >> > >> > Braden
>> >> > >> >
>> >> > >> >
>> >> > >> > On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com>
>> >> wrote:
>> >> > >> >
>> >> > >> > > Yes, let's get this cleared up - confused myself.
>> >> > >> > >
>> >> > >> > >
>> >> > >> > > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <
>> >> anis.kadri@gmail.com>
>> >> > >> > wrote:
>> >> > >> > >
>> >> > >> > > > 3.1.0 is coincidental and it's temporary for this release
>> >> because
>> >> > I
>> >> > >> > > > wasn't sure where to get the code from and didn't want to
>> >> > compromise
>> >> > >> > > > master or dev. I could have called it something else.
>> >> > >> > > >
>> >> > >> > > > Jesse, I'd advise you to commit to dev. Everything will be
>> >> merged
>> >> > to
>> >> > >> > > > master eventually.
>> >> > >> > > >
>> >> > >> > > > So to re-iterate the process: right now it's "dev -> master"
>> >> and
>> >> > >> > > > eventually it will be "master -> (independant) plugin
>> version".
>> >> > >> > > > amarite?
>> >> > >> > > >
>> >> > >> > > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <
>> >> bowserj@gmail.com>
>> >> > >> > wrote:
>> >> > >> > > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <
>> >> > >> agrieve@chromium.org
>> >> > >> > >
>> >> > >> > > > wrote:
>> >> > >> > > > >> Plugins are not tagged nor branched along with platforms.
>> >> They
>> >> > are
>> >> > >> > > > releases
>> >> > >> > > > >> completely independently.
>> >> > >> > > > >>
>> >> > >> > > > >> Commit to the "dev" branch always.
>> >> > >> > > > >
>> >> > >> > > > > AND FOREVER!!!!!11!!eleventyone!!!
>> >> > >> > > > >
>> >> > >> > > > > Seriously, can't we have a stable branch instead? Having
>> the
>> >> dev
>> >> > >> > > > > branch for dev on plugins and having master for dev on
>> >> > platforms is
>> >> > >> > > > > stupid and makes it harder to do work.
>> >> > >> > > >
>> >> > >> > >
>> >> > >> >
>> >> > >>
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Carlos Santana
>> > <cs...@gmail.com>
>> >
>>
>>
>>
>> --
>> Carlos Santana
>> <cs...@gmail.com>
>>
>
>
Re: 3.1 Release
Posted by Steven Gill <st...@gmail.com>.
Michael,
Good point. I think the issue arrises if some of our users keep using 3.0,
install plugins using the git url (master branch) and then try to remove
the plugins using the 3.0 documentation. When the master branch gets
updated, it won't have core in the ID. This will make the remove
instructions incorrect.
An upgrade guide/blog post actually sounds like the best way to handle this
issue.
I am going to pick up where Anis left of and aim to do a plugin release
later this afternoon
-Steve
On Wed, Sep 25, 2013 at 6:45 AM, Carlos Santana <cs...@gmail.com>wrote:
> It could be a doc or or blog post, I would suggest blog post for plugins
> for more details about dealing with registry since those have a faster pace
>
> --Carlos
>
>
>
> On Wed, Sep 25, 2013 at 9:43 AM, Carlos Santana <csantana23@gmail.com
> >wrote:
>
> > Would suggest we document a simple workflow document "Upgrade Guide
> > Cordova CLI/PlugMan 3.0 to 3.1"
> > Same way that we do for the platforms on going over the details in a
> > single document.
> >
> > --Carlos
> >
> >
> > On Wed, Sep 25, 2013 at 9:38 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> >> I think the 3.0 instructions of removing the old plugin with the old ID
> >> remain correct even after we update the registry. Thats because when
> >> removing plugins from a workspace you use the ID of whats locally
> >> installed.
> >>
> >> So, to upgrade, users would have the use the 3.0 uninstall guide and the
> >> 3.1 install guide.. I think?
> >>
> >> -Michal
> >>
> >>
> >> On Wed, Sep 25, 2013 at 7:31 AM, Anis KADRI <an...@gmail.com>
> wrote:
> >>
> >> > That's a good summary. I am going to be fixing the reference problem
> >> > shortly and merge them back to the `dev` branch. Not sure if all of
> >> > Jesse's changes have made it to the `dev` branch yet.
> >> >
> >> > The `edge` docs have already been updated (see CB-4493)
> >> >
> >> > The `3.0` docs will have to be updated once we merge `dev` back to
> >> > `master` (which I hope we will before we release 3.1).
> >> >
> >> >
> >> > On Wed, Sep 25, 2013 at 1:25 AM, Steven Gill <st...@gmail.com>
> >> > wrote:
> >> > > I realize why Anis decided to do a new branch (3.1.0) because he
> >> didn't
> >> > > want to mess up dev/master. Before we release 3.1.0 we need to do a
> >> > plugin
> >> > > release based off of
> >> > http://wiki.apache.org/cordova/StepsForPluginRelease.
> >> > > Jesse has changes for the plugins that he has pushed to dev now
> based
> >> on
> >> > > this email thread. He needs these changes to be in the next plugin
> >> > release
> >> > > we are doing for the 3.1.0 release.
> >> > >
> >> > > If I am understanding this correctly, removing core from ID was not
> >> > > something we want in master due to 3.0.0 support. But this ID change
> >> > should
> >> > > have been done on dev before creating the 3.1.0 branch. The 3.0.0
> docs
> >> > get
> >> > > users to install plugins using the git url. The problem is that the
> >> 3.0.0
> >> > > docs instruct our users to use the ID for plugin removal. Obviously
> >> if we
> >> > > change the ID, the remove documentation for 3.0.0 would be wrong.
> >> > >
> >> > > We have two options here as far as I can tell
> >> > >
> >> > > 1) Leave master alone for the next month or two and give people time
> >> to
> >> > > migrate to 3.1
> >> > > 2) Update the 3.0 documentation to refer to updated id, Push the
> >> updated
> >> > ID
> >> > > to dev then master.
> >> > >
> >> > > Things that need to be done
> >> > > - Fix incorrect references to the old ID (last comment on
> >> > > https://issues.apache.org/jira/browse/CB-4889)
> >> > > - Merge these changes into dev (they really should be on dev if
> that
> >> is
> >> > > where we all the work done)
> >> > > - Follow steps on
> >> http://wiki.apache.org/cordova/StepsForPluginReleaseand
> >> > > publish these plugins on our registry. This should include Jesse's
> >> work
> >> > as
> >> > > well.
> >> > > - Update edge docs to refer to registry for plugin installation
> (not
> >> > sure
> >> > > if this has been done)
> >> > > - Update 3.0.0 documentation if we decide option 2 from above is
> the
> >> way
> >> > > to go
> >> > > - Tag docs 3.1.0-rc1
> >> > >
> >> > > I volunteer to take the lead on getting the plugins released +
> tested
> >> > > (supposed to be today according to Andrew's timeline) for tomorrow
> >> > > afternoon. I can get to the docs after that.
> >> > >
> >> > > Before I dive into this full steam, any feedback on above?
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny <mm...@chromium.org>
> >> > wrote:
> >> > >
> >> > >> Just to be super duper clear: the reason to work on 'dev' branch of
> >> > plugins
> >> > >> is not some process decision we are imposing, its a direct
> >> requirement
> >> > >> imposed on us by the limitations of our tools (specifically, the
> >> state
> >> > of
> >> > >> the registry as it was with 3.0 launch).
> >> > >>
> >> > >> We discussed this in-depth just a week ago (Read "About plugins in
> >> > 3.1"),
> >> > >> and I think several other times over the last month, if you would
> >> like
> >> > to
> >> > >> read up on the details look there.
> >> > >>
> >> > >> No one likes the situation, we've been making headway into fixing
> it
> >> > ever
> >> > >> since we discovered the problem, and it can be resolved as soon as
> >> users
> >> > >> upgrade from 3.0 (maybe that means we can switch after 3.1 release,
> >> > maybe
> >> > >> that means we wait for some 3-months deprecation time, not sure).
> >> > >>
> >> > >> -Michal
> >> > >>
> >> > >>
> >> > >> On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <
> >> > braden@chromium.org
> >> > >> >wrote:
> >> > >>
> >> > >> > I agree with Joe that developing on anything other than master
> >> sucks.
> >> > But
> >> > >> > unfortunately, our hands are tied in the near term because the
> >> > registry
> >> > >> > doesn't know to fetch plugins from anywhere else. Also it makes
> >> life
> >> > >> easier
> >> > >> > for being who are installing plugins from git URLs.
> >> > >> >
> >> > >> > I think we eventually want to get to a world where 99% of plugin
> >> > installs
> >> > >> > are happening from the registry, the registry knows how to fetch
> >> tags,
> >> > >> and
> >> > >> > people who are using git URLs directly know what they're doing
> and
> >> > want
> >> > >> the
> >> > >> > dev version. (Also you can specify branches with #gitref in the
> >> URL,
> >> > so
> >> > >> > there's flexibility there.) But we're not there yet.
> >> > >> >
> >> > >> > Braden
> >> > >> >
> >> > >> >
> >> > >> > On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com>
> >> wrote:
> >> > >> >
> >> > >> > > Yes, let's get this cleared up - confused myself.
> >> > >> > >
> >> > >> > >
> >> > >> > > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <
> >> anis.kadri@gmail.com>
> >> > >> > wrote:
> >> > >> > >
> >> > >> > > > 3.1.0 is coincidental and it's temporary for this release
> >> because
> >> > I
> >> > >> > > > wasn't sure where to get the code from and didn't want to
> >> > compromise
> >> > >> > > > master or dev. I could have called it something else.
> >> > >> > > >
> >> > >> > > > Jesse, I'd advise you to commit to dev. Everything will be
> >> merged
> >> > to
> >> > >> > > > master eventually.
> >> > >> > > >
> >> > >> > > > So to re-iterate the process: right now it's "dev -> master"
> >> and
> >> > >> > > > eventually it will be "master -> (independant) plugin
> version".
> >> > >> > > > amarite?
> >> > >> > > >
> >> > >> > > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <
> >> bowserj@gmail.com>
> >> > >> > wrote:
> >> > >> > > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <
> >> > >> agrieve@chromium.org
> >> > >> > >
> >> > >> > > > wrote:
> >> > >> > > > >> Plugins are not tagged nor branched along with platforms.
> >> They
> >> > are
> >> > >> > > > releases
> >> > >> > > > >> completely independently.
> >> > >> > > > >>
> >> > >> > > > >> Commit to the "dev" branch always.
> >> > >> > > > >
> >> > >> > > > > AND FOREVER!!!!!11!!eleventyone!!!
> >> > >> > > > >
> >> > >> > > > > Seriously, can't we have a stable branch instead? Having
> the
> >> dev
> >> > >> > > > > branch for dev on plugins and having master for dev on
> >> > platforms is
> >> > >> > > > > stupid and makes it harder to do work.
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >>
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: 3.1 Release
Posted by Carlos Santana <cs...@gmail.com>.
It could be a doc or or blog post, I would suggest blog post for plugins
for more details about dealing with registry since those have a faster pace
--Carlos
On Wed, Sep 25, 2013 at 9:43 AM, Carlos Santana <cs...@gmail.com>wrote:
> Would suggest we document a simple workflow document "Upgrade Guide
> Cordova CLI/PlugMan 3.0 to 3.1"
> Same way that we do for the platforms on going over the details in a
> single document.
>
> --Carlos
>
>
> On Wed, Sep 25, 2013 at 9:38 AM, Michal Mocny <mm...@chromium.org> wrote:
>
>> I think the 3.0 instructions of removing the old plugin with the old ID
>> remain correct even after we update the registry. Thats because when
>> removing plugins from a workspace you use the ID of whats locally
>> installed.
>>
>> So, to upgrade, users would have the use the 3.0 uninstall guide and the
>> 3.1 install guide.. I think?
>>
>> -Michal
>>
>>
>> On Wed, Sep 25, 2013 at 7:31 AM, Anis KADRI <an...@gmail.com> wrote:
>>
>> > That's a good summary. I am going to be fixing the reference problem
>> > shortly and merge them back to the `dev` branch. Not sure if all of
>> > Jesse's changes have made it to the `dev` branch yet.
>> >
>> > The `edge` docs have already been updated (see CB-4493)
>> >
>> > The `3.0` docs will have to be updated once we merge `dev` back to
>> > `master` (which I hope we will before we release 3.1).
>> >
>> >
>> > On Wed, Sep 25, 2013 at 1:25 AM, Steven Gill <st...@gmail.com>
>> > wrote:
>> > > I realize why Anis decided to do a new branch (3.1.0) because he
>> didn't
>> > > want to mess up dev/master. Before we release 3.1.0 we need to do a
>> > plugin
>> > > release based off of
>> > http://wiki.apache.org/cordova/StepsForPluginRelease.
>> > > Jesse has changes for the plugins that he has pushed to dev now based
>> on
>> > > this email thread. He needs these changes to be in the next plugin
>> > release
>> > > we are doing for the 3.1.0 release.
>> > >
>> > > If I am understanding this correctly, removing core from ID was not
>> > > something we want in master due to 3.0.0 support. But this ID change
>> > should
>> > > have been done on dev before creating the 3.1.0 branch. The 3.0.0 docs
>> > get
>> > > users to install plugins using the git url. The problem is that the
>> 3.0.0
>> > > docs instruct our users to use the ID for plugin removal. Obviously
>> if we
>> > > change the ID, the remove documentation for 3.0.0 would be wrong.
>> > >
>> > > We have two options here as far as I can tell
>> > >
>> > > 1) Leave master alone for the next month or two and give people time
>> to
>> > > migrate to 3.1
>> > > 2) Update the 3.0 documentation to refer to updated id, Push the
>> updated
>> > ID
>> > > to dev then master.
>> > >
>> > > Things that need to be done
>> > > - Fix incorrect references to the old ID (last comment on
>> > > https://issues.apache.org/jira/browse/CB-4889)
>> > > - Merge these changes into dev (they really should be on dev if that
>> is
>> > > where we all the work done)
>> > > - Follow steps on
>> http://wiki.apache.org/cordova/StepsForPluginReleaseand
>> > > publish these plugins on our registry. This should include Jesse's
>> work
>> > as
>> > > well.
>> > > - Update edge docs to refer to registry for plugin installation (not
>> > sure
>> > > if this has been done)
>> > > - Update 3.0.0 documentation if we decide option 2 from above is the
>> way
>> > > to go
>> > > - Tag docs 3.1.0-rc1
>> > >
>> > > I volunteer to take the lead on getting the plugins released + tested
>> > > (supposed to be today according to Andrew's timeline) for tomorrow
>> > > afternoon. I can get to the docs after that.
>> > >
>> > > Before I dive into this full steam, any feedback on above?
>> > >
>> > >
>> > >
>> > >
>> > > On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny <mm...@chromium.org>
>> > wrote:
>> > >
>> > >> Just to be super duper clear: the reason to work on 'dev' branch of
>> > plugins
>> > >> is not some process decision we are imposing, its a direct
>> requirement
>> > >> imposed on us by the limitations of our tools (specifically, the
>> state
>> > of
>> > >> the registry as it was with 3.0 launch).
>> > >>
>> > >> We discussed this in-depth just a week ago (Read "About plugins in
>> > 3.1"),
>> > >> and I think several other times over the last month, if you would
>> like
>> > to
>> > >> read up on the details look there.
>> > >>
>> > >> No one likes the situation, we've been making headway into fixing it
>> > ever
>> > >> since we discovered the problem, and it can be resolved as soon as
>> users
>> > >> upgrade from 3.0 (maybe that means we can switch after 3.1 release,
>> > maybe
>> > >> that means we wait for some 3-months deprecation time, not sure).
>> > >>
>> > >> -Michal
>> > >>
>> > >>
>> > >> On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <
>> > braden@chromium.org
>> > >> >wrote:
>> > >>
>> > >> > I agree with Joe that developing on anything other than master
>> sucks.
>> > But
>> > >> > unfortunately, our hands are tied in the near term because the
>> > registry
>> > >> > doesn't know to fetch plugins from anywhere else. Also it makes
>> life
>> > >> easier
>> > >> > for being who are installing plugins from git URLs.
>> > >> >
>> > >> > I think we eventually want to get to a world where 99% of plugin
>> > installs
>> > >> > are happening from the registry, the registry knows how to fetch
>> tags,
>> > >> and
>> > >> > people who are using git URLs directly know what they're doing and
>> > want
>> > >> the
>> > >> > dev version. (Also you can specify branches with #gitref in the
>> URL,
>> > so
>> > >> > there's flexibility there.) But we're not there yet.
>> > >> >
>> > >> > Braden
>> > >> >
>> > >> >
>> > >> > On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com>
>> wrote:
>> > >> >
>> > >> > > Yes, let's get this cleared up - confused myself.
>> > >> > >
>> > >> > >
>> > >> > > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <
>> anis.kadri@gmail.com>
>> > >> > wrote:
>> > >> > >
>> > >> > > > 3.1.0 is coincidental and it's temporary for this release
>> because
>> > I
>> > >> > > > wasn't sure where to get the code from and didn't want to
>> > compromise
>> > >> > > > master or dev. I could have called it something else.
>> > >> > > >
>> > >> > > > Jesse, I'd advise you to commit to dev. Everything will be
>> merged
>> > to
>> > >> > > > master eventually.
>> > >> > > >
>> > >> > > > So to re-iterate the process: right now it's "dev -> master"
>> and
>> > >> > > > eventually it will be "master -> (independant) plugin version".
>> > >> > > > amarite?
>> > >> > > >
>> > >> > > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <
>> bowserj@gmail.com>
>> > >> > wrote:
>> > >> > > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <
>> > >> agrieve@chromium.org
>> > >> > >
>> > >> > > > wrote:
>> > >> > > > >> Plugins are not tagged nor branched along with platforms.
>> They
>> > are
>> > >> > > > releases
>> > >> > > > >> completely independently.
>> > >> > > > >>
>> > >> > > > >> Commit to the "dev" branch always.
>> > >> > > > >
>> > >> > > > > AND FOREVER!!!!!11!!eleventyone!!!
>> > >> > > > >
>> > >> > > > > Seriously, can't we have a stable branch instead? Having the
>> dev
>> > >> > > > > branch for dev on plugins and having master for dev on
>> > platforms is
>> > >> > > > > stupid and makes it harder to do work.
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>>
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
--
Carlos Santana
<cs...@gmail.com>
Re: 3.1 Release
Posted by Carlos Santana <cs...@gmail.com>.
Would suggest we document a simple workflow document "Upgrade Guide Cordova
CLI/PlugMan 3.0 to 3.1"
Same way that we do for the platforms on going over the details in a single
document.
--Carlos
On Wed, Sep 25, 2013 at 9:38 AM, Michal Mocny <mm...@chromium.org> wrote:
> I think the 3.0 instructions of removing the old plugin with the old ID
> remain correct even after we update the registry. Thats because when
> removing plugins from a workspace you use the ID of whats locally
> installed.
>
> So, to upgrade, users would have the use the 3.0 uninstall guide and the
> 3.1 install guide.. I think?
>
> -Michal
>
>
> On Wed, Sep 25, 2013 at 7:31 AM, Anis KADRI <an...@gmail.com> wrote:
>
> > That's a good summary. I am going to be fixing the reference problem
> > shortly and merge them back to the `dev` branch. Not sure if all of
> > Jesse's changes have made it to the `dev` branch yet.
> >
> > The `edge` docs have already been updated (see CB-4493)
> >
> > The `3.0` docs will have to be updated once we merge `dev` back to
> > `master` (which I hope we will before we release 3.1).
> >
> >
> > On Wed, Sep 25, 2013 at 1:25 AM, Steven Gill <st...@gmail.com>
> > wrote:
> > > I realize why Anis decided to do a new branch (3.1.0) because he didn't
> > > want to mess up dev/master. Before we release 3.1.0 we need to do a
> > plugin
> > > release based off of
> > http://wiki.apache.org/cordova/StepsForPluginRelease.
> > > Jesse has changes for the plugins that he has pushed to dev now based
> on
> > > this email thread. He needs these changes to be in the next plugin
> > release
> > > we are doing for the 3.1.0 release.
> > >
> > > If I am understanding this correctly, removing core from ID was not
> > > something we want in master due to 3.0.0 support. But this ID change
> > should
> > > have been done on dev before creating the 3.1.0 branch. The 3.0.0 docs
> > get
> > > users to install plugins using the git url. The problem is that the
> 3.0.0
> > > docs instruct our users to use the ID for plugin removal. Obviously if
> we
> > > change the ID, the remove documentation for 3.0.0 would be wrong.
> > >
> > > We have two options here as far as I can tell
> > >
> > > 1) Leave master alone for the next month or two and give people time to
> > > migrate to 3.1
> > > 2) Update the 3.0 documentation to refer to updated id, Push the
> updated
> > ID
> > > to dev then master.
> > >
> > > Things that need to be done
> > > - Fix incorrect references to the old ID (last comment on
> > > https://issues.apache.org/jira/browse/CB-4889)
> > > - Merge these changes into dev (they really should be on dev if that
> is
> > > where we all the work done)
> > > - Follow steps on
> http://wiki.apache.org/cordova/StepsForPluginReleaseand
> > > publish these plugins on our registry. This should include Jesse's work
> > as
> > > well.
> > > - Update edge docs to refer to registry for plugin installation (not
> > sure
> > > if this has been done)
> > > - Update 3.0.0 documentation if we decide option 2 from above is the
> way
> > > to go
> > > - Tag docs 3.1.0-rc1
> > >
> > > I volunteer to take the lead on getting the plugins released + tested
> > > (supposed to be today according to Andrew's timeline) for tomorrow
> > > afternoon. I can get to the docs after that.
> > >
> > > Before I dive into this full steam, any feedback on above?
> > >
> > >
> > >
> > >
> > > On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >
> > >> Just to be super duper clear: the reason to work on 'dev' branch of
> > plugins
> > >> is not some process decision we are imposing, its a direct requirement
> > >> imposed on us by the limitations of our tools (specifically, the state
> > of
> > >> the registry as it was with 3.0 launch).
> > >>
> > >> We discussed this in-depth just a week ago (Read "About plugins in
> > 3.1"),
> > >> and I think several other times over the last month, if you would like
> > to
> > >> read up on the details look there.
> > >>
> > >> No one likes the situation, we've been making headway into fixing it
> > ever
> > >> since we discovered the problem, and it can be resolved as soon as
> users
> > >> upgrade from 3.0 (maybe that means we can switch after 3.1 release,
> > maybe
> > >> that means we wait for some 3-months deprecation time, not sure).
> > >>
> > >> -Michal
> > >>
> > >>
> > >> On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <
> > braden@chromium.org
> > >> >wrote:
> > >>
> > >> > I agree with Joe that developing on anything other than master
> sucks.
> > But
> > >> > unfortunately, our hands are tied in the near term because the
> > registry
> > >> > doesn't know to fetch plugins from anywhere else. Also it makes life
> > >> easier
> > >> > for being who are installing plugins from git URLs.
> > >> >
> > >> > I think we eventually want to get to a world where 99% of plugin
> > installs
> > >> > are happening from the registry, the registry knows how to fetch
> tags,
> > >> and
> > >> > people who are using git URLs directly know what they're doing and
> > want
> > >> the
> > >> > dev version. (Also you can specify branches with #gitref in the URL,
> > so
> > >> > there's flexibility there.) But we're not there yet.
> > >> >
> > >> > Braden
> > >> >
> > >> >
> > >> > On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com> wrote:
> > >> >
> > >> > > Yes, let's get this cleared up - confused myself.
> > >> > >
> > >> > >
> > >> > > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <anis.kadri@gmail.com
> >
> > >> > wrote:
> > >> > >
> > >> > > > 3.1.0 is coincidental and it's temporary for this release
> because
> > I
> > >> > > > wasn't sure where to get the code from and didn't want to
> > compromise
> > >> > > > master or dev. I could have called it something else.
> > >> > > >
> > >> > > > Jesse, I'd advise you to commit to dev. Everything will be
> merged
> > to
> > >> > > > master eventually.
> > >> > > >
> > >> > > > So to re-iterate the process: right now it's "dev -> master" and
> > >> > > > eventually it will be "master -> (independant) plugin version".
> > >> > > > amarite?
> > >> > > >
> > >> > > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <bowserj@gmail.com
> >
> > >> > wrote:
> > >> > > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <
> > >> agrieve@chromium.org
> > >> > >
> > >> > > > wrote:
> > >> > > > >> Plugins are not tagged nor branched along with platforms.
> They
> > are
> > >> > > > releases
> > >> > > > >> completely independently.
> > >> > > > >>
> > >> > > > >> Commit to the "dev" branch always.
> > >> > > > >
> > >> > > > > AND FOREVER!!!!!11!!eleventyone!!!
> > >> > > > >
> > >> > > > > Seriously, can't we have a stable branch instead? Having the
> dev
> > >> > > > > branch for dev on plugins and having master for dev on
> > platforms is
> > >> > > > > stupid and makes it harder to do work.
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: 3.1 Release
Posted by Michal Mocny <mm...@chromium.org>.
I think the 3.0 instructions of removing the old plugin with the old ID
remain correct even after we update the registry. Thats because when
removing plugins from a workspace you use the ID of whats locally installed.
So, to upgrade, users would have the use the 3.0 uninstall guide and the
3.1 install guide.. I think?
-Michal
On Wed, Sep 25, 2013 at 7:31 AM, Anis KADRI <an...@gmail.com> wrote:
> That's a good summary. I am going to be fixing the reference problem
> shortly and merge them back to the `dev` branch. Not sure if all of
> Jesse's changes have made it to the `dev` branch yet.
>
> The `edge` docs have already been updated (see CB-4493)
>
> The `3.0` docs will have to be updated once we merge `dev` back to
> `master` (which I hope we will before we release 3.1).
>
>
> On Wed, Sep 25, 2013 at 1:25 AM, Steven Gill <st...@gmail.com>
> wrote:
> > I realize why Anis decided to do a new branch (3.1.0) because he didn't
> > want to mess up dev/master. Before we release 3.1.0 we need to do a
> plugin
> > release based off of
> http://wiki.apache.org/cordova/StepsForPluginRelease.
> > Jesse has changes for the plugins that he has pushed to dev now based on
> > this email thread. He needs these changes to be in the next plugin
> release
> > we are doing for the 3.1.0 release.
> >
> > If I am understanding this correctly, removing core from ID was not
> > something we want in master due to 3.0.0 support. But this ID change
> should
> > have been done on dev before creating the 3.1.0 branch. The 3.0.0 docs
> get
> > users to install plugins using the git url. The problem is that the 3.0.0
> > docs instruct our users to use the ID for plugin removal. Obviously if we
> > change the ID, the remove documentation for 3.0.0 would be wrong.
> >
> > We have two options here as far as I can tell
> >
> > 1) Leave master alone for the next month or two and give people time to
> > migrate to 3.1
> > 2) Update the 3.0 documentation to refer to updated id, Push the updated
> ID
> > to dev then master.
> >
> > Things that need to be done
> > - Fix incorrect references to the old ID (last comment on
> > https://issues.apache.org/jira/browse/CB-4889)
> > - Merge these changes into dev (they really should be on dev if that is
> > where we all the work done)
> > - Follow steps on http://wiki.apache.org/cordova/StepsForPluginReleaseand
> > publish these plugins on our registry. This should include Jesse's work
> as
> > well.
> > - Update edge docs to refer to registry for plugin installation (not
> sure
> > if this has been done)
> > - Update 3.0.0 documentation if we decide option 2 from above is the way
> > to go
> > - Tag docs 3.1.0-rc1
> >
> > I volunteer to take the lead on getting the plugins released + tested
> > (supposed to be today according to Andrew's timeline) for tomorrow
> > afternoon. I can get to the docs after that.
> >
> > Before I dive into this full steam, any feedback on above?
> >
> >
> >
> >
> > On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> >> Just to be super duper clear: the reason to work on 'dev' branch of
> plugins
> >> is not some process decision we are imposing, its a direct requirement
> >> imposed on us by the limitations of our tools (specifically, the state
> of
> >> the registry as it was with 3.0 launch).
> >>
> >> We discussed this in-depth just a week ago (Read "About plugins in
> 3.1"),
> >> and I think several other times over the last month, if you would like
> to
> >> read up on the details look there.
> >>
> >> No one likes the situation, we've been making headway into fixing it
> ever
> >> since we discovered the problem, and it can be resolved as soon as users
> >> upgrade from 3.0 (maybe that means we can switch after 3.1 release,
> maybe
> >> that means we wait for some 3-months deprecation time, not sure).
> >>
> >> -Michal
> >>
> >>
> >> On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <
> braden@chromium.org
> >> >wrote:
> >>
> >> > I agree with Joe that developing on anything other than master sucks.
> But
> >> > unfortunately, our hands are tied in the near term because the
> registry
> >> > doesn't know to fetch plugins from anywhere else. Also it makes life
> >> easier
> >> > for being who are installing plugins from git URLs.
> >> >
> >> > I think we eventually want to get to a world where 99% of plugin
> installs
> >> > are happening from the registry, the registry knows how to fetch tags,
> >> and
> >> > people who are using git URLs directly know what they're doing and
> want
> >> the
> >> > dev version. (Also you can specify branches with #gitref in the URL,
> so
> >> > there's flexibility there.) But we're not there yet.
> >> >
> >> > Braden
> >> >
> >> >
> >> > On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com> wrote:
> >> >
> >> > > Yes, let's get this cleared up - confused myself.
> >> > >
> >> > >
> >> > > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <an...@gmail.com>
> >> > wrote:
> >> > >
> >> > > > 3.1.0 is coincidental and it's temporary for this release because
> I
> >> > > > wasn't sure where to get the code from and didn't want to
> compromise
> >> > > > master or dev. I could have called it something else.
> >> > > >
> >> > > > Jesse, I'd advise you to commit to dev. Everything will be merged
> to
> >> > > > master eventually.
> >> > > >
> >> > > > So to re-iterate the process: right now it's "dev -> master" and
> >> > > > eventually it will be "master -> (independant) plugin version".
> >> > > > amarite?
> >> > > >
> >> > > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <bo...@gmail.com>
> >> > wrote:
> >> > > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <
> >> agrieve@chromium.org
> >> > >
> >> > > > wrote:
> >> > > > >> Plugins are not tagged nor branched along with platforms. They
> are
> >> > > > releases
> >> > > > >> completely independently.
> >> > > > >>
> >> > > > >> Commit to the "dev" branch always.
> >> > > > >
> >> > > > > AND FOREVER!!!!!11!!eleventyone!!!
> >> > > > >
> >> > > > > Seriously, can't we have a stable branch instead? Having the dev
> >> > > > > branch for dev on plugins and having master for dev on
> platforms is
> >> > > > > stupid and makes it harder to do work.
> >> > > >
> >> > >
> >> >
> >>
>
Re: 3.1 Release
Posted by Anis KADRI <an...@gmail.com>.
That's a good summary. I am going to be fixing the reference problem
shortly and merge them back to the `dev` branch. Not sure if all of
Jesse's changes have made it to the `dev` branch yet.
The `edge` docs have already been updated (see CB-4493)
The `3.0` docs will have to be updated once we merge `dev` back to
`master` (which I hope we will before we release 3.1).
On Wed, Sep 25, 2013 at 1:25 AM, Steven Gill <st...@gmail.com> wrote:
> I realize why Anis decided to do a new branch (3.1.0) because he didn't
> want to mess up dev/master. Before we release 3.1.0 we need to do a plugin
> release based off of http://wiki.apache.org/cordova/StepsForPluginRelease.
> Jesse has changes for the plugins that he has pushed to dev now based on
> this email thread. He needs these changes to be in the next plugin release
> we are doing for the 3.1.0 release.
>
> If I am understanding this correctly, removing core from ID was not
> something we want in master due to 3.0.0 support. But this ID change should
> have been done on dev before creating the 3.1.0 branch. The 3.0.0 docs get
> users to install plugins using the git url. The problem is that the 3.0.0
> docs instruct our users to use the ID for plugin removal. Obviously if we
> change the ID, the remove documentation for 3.0.0 would be wrong.
>
> We have two options here as far as I can tell
>
> 1) Leave master alone for the next month or two and give people time to
> migrate to 3.1
> 2) Update the 3.0 documentation to refer to updated id, Push the updated ID
> to dev then master.
>
> Things that need to be done
> - Fix incorrect references to the old ID (last comment on
> https://issues.apache.org/jira/browse/CB-4889)
> - Merge these changes into dev (they really should be on dev if that is
> where we all the work done)
> - Follow steps on http://wiki.apache.org/cordova/StepsForPluginRelease and
> publish these plugins on our registry. This should include Jesse's work as
> well.
> - Update edge docs to refer to registry for plugin installation (not sure
> if this has been done)
> - Update 3.0.0 documentation if we decide option 2 from above is the way
> to go
> - Tag docs 3.1.0-rc1
>
> I volunteer to take the lead on getting the plugins released + tested
> (supposed to be today according to Andrew's timeline) for tomorrow
> afternoon. I can get to the docs after that.
>
> Before I dive into this full steam, any feedback on above?
>
>
>
>
> On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny <mm...@chromium.org> wrote:
>
>> Just to be super duper clear: the reason to work on 'dev' branch of plugins
>> is not some process decision we are imposing, its a direct requirement
>> imposed on us by the limitations of our tools (specifically, the state of
>> the registry as it was with 3.0 launch).
>>
>> We discussed this in-depth just a week ago (Read "About plugins in 3.1"),
>> and I think several other times over the last month, if you would like to
>> read up on the details look there.
>>
>> No one likes the situation, we've been making headway into fixing it ever
>> since we discovered the problem, and it can be resolved as soon as users
>> upgrade from 3.0 (maybe that means we can switch after 3.1 release, maybe
>> that means we wait for some 3-months deprecation time, not sure).
>>
>> -Michal
>>
>>
>> On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <braden@chromium.org
>> >wrote:
>>
>> > I agree with Joe that developing on anything other than master sucks. But
>> > unfortunately, our hands are tied in the near term because the registry
>> > doesn't know to fetch plugins from anywhere else. Also it makes life
>> easier
>> > for being who are installing plugins from git URLs.
>> >
>> > I think we eventually want to get to a world where 99% of plugin installs
>> > are happening from the registry, the registry knows how to fetch tags,
>> and
>> > people who are using git URLs directly know what they're doing and want
>> the
>> > dev version. (Also you can specify branches with #gitref in the URL, so
>> > there's flexibility there.) But we're not there yet.
>> >
>> > Braden
>> >
>> >
>> > On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com> wrote:
>> >
>> > > Yes, let's get this cleared up - confused myself.
>> > >
>> > >
>> > > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <an...@gmail.com>
>> > wrote:
>> > >
>> > > > 3.1.0 is coincidental and it's temporary for this release because I
>> > > > wasn't sure where to get the code from and didn't want to compromise
>> > > > master or dev. I could have called it something else.
>> > > >
>> > > > Jesse, I'd advise you to commit to dev. Everything will be merged to
>> > > > master eventually.
>> > > >
>> > > > So to re-iterate the process: right now it's "dev -> master" and
>> > > > eventually it will be "master -> (independant) plugin version".
>> > > > amarite?
>> > > >
>> > > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <bo...@gmail.com>
>> > wrote:
>> > > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <
>> agrieve@chromium.org
>> > >
>> > > > wrote:
>> > > > >> Plugins are not tagged nor branched along with platforms. They are
>> > > > releases
>> > > > >> completely independently.
>> > > > >>
>> > > > >> Commit to the "dev" branch always.
>> > > > >
>> > > > > AND FOREVER!!!!!11!!eleventyone!!!
>> > > > >
>> > > > > Seriously, can't we have a stable branch instead? Having the dev
>> > > > > branch for dev on plugins and having master for dev on platforms is
>> > > > > stupid and makes it harder to do work.
>> > > >
>> > >
>> >
>>
Re: 3.1 Release
Posted by Steven Gill <st...@gmail.com>.
I realize why Anis decided to do a new branch (3.1.0) because he didn't
want to mess up dev/master. Before we release 3.1.0 we need to do a plugin
release based off of http://wiki.apache.org/cordova/StepsForPluginRelease.
Jesse has changes for the plugins that he has pushed to dev now based on
this email thread. He needs these changes to be in the next plugin release
we are doing for the 3.1.0 release.
If I am understanding this correctly, removing core from ID was not
something we want in master due to 3.0.0 support. But this ID change should
have been done on dev before creating the 3.1.0 branch. The 3.0.0 docs get
users to install plugins using the git url. The problem is that the 3.0.0
docs instruct our users to use the ID for plugin removal. Obviously if we
change the ID, the remove documentation for 3.0.0 would be wrong.
We have two options here as far as I can tell
1) Leave master alone for the next month or two and give people time to
migrate to 3.1
2) Update the 3.0 documentation to refer to updated id, Push the updated ID
to dev then master.
Things that need to be done
- Fix incorrect references to the old ID (last comment on
https://issues.apache.org/jira/browse/CB-4889)
- Merge these changes into dev (they really should be on dev if that is
where we all the work done)
- Follow steps on http://wiki.apache.org/cordova/StepsForPluginRelease and
publish these plugins on our registry. This should include Jesse's work as
well.
- Update edge docs to refer to registry for plugin installation (not sure
if this has been done)
- Update 3.0.0 documentation if we decide option 2 from above is the way
to go
- Tag docs 3.1.0-rc1
I volunteer to take the lead on getting the plugins released + tested
(supposed to be today according to Andrew's timeline) for tomorrow
afternoon. I can get to the docs after that.
Before I dive into this full steam, any feedback on above?
On Tue, Sep 24, 2013 at 8:08 AM, Michal Mocny <mm...@chromium.org> wrote:
> Just to be super duper clear: the reason to work on 'dev' branch of plugins
> is not some process decision we are imposing, its a direct requirement
> imposed on us by the limitations of our tools (specifically, the state of
> the registry as it was with 3.0 launch).
>
> We discussed this in-depth just a week ago (Read "About plugins in 3.1"),
> and I think several other times over the last month, if you would like to
> read up on the details look there.
>
> No one likes the situation, we've been making headway into fixing it ever
> since we discovered the problem, and it can be resolved as soon as users
> upgrade from 3.0 (maybe that means we can switch after 3.1 release, maybe
> that means we wait for some 3-months deprecation time, not sure).
>
> -Michal
>
>
> On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <braden@chromium.org
> >wrote:
>
> > I agree with Joe that developing on anything other than master sucks. But
> > unfortunately, our hands are tied in the near term because the registry
> > doesn't know to fetch plugins from anywhere else. Also it makes life
> easier
> > for being who are installing plugins from git URLs.
> >
> > I think we eventually want to get to a world where 99% of plugin installs
> > are happening from the registry, the registry knows how to fetch tags,
> and
> > people who are using git URLs directly know what they're doing and want
> the
> > dev version. (Also you can specify branches with #gitref in the URL, so
> > there's flexibility there.) But we're not there yet.
> >
> > Braden
> >
> >
> > On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com> wrote:
> >
> > > Yes, let's get this cleared up - confused myself.
> > >
> > >
> > > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <an...@gmail.com>
> > wrote:
> > >
> > > > 3.1.0 is coincidental and it's temporary for this release because I
> > > > wasn't sure where to get the code from and didn't want to compromise
> > > > master or dev. I could have called it something else.
> > > >
> > > > Jesse, I'd advise you to commit to dev. Everything will be merged to
> > > > master eventually.
> > > >
> > > > So to re-iterate the process: right now it's "dev -> master" and
> > > > eventually it will be "master -> (independant) plugin version".
> > > > amarite?
> > > >
> > > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <bo...@gmail.com>
> > wrote:
> > > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <
> agrieve@chromium.org
> > >
> > > > wrote:
> > > > >> Plugins are not tagged nor branched along with platforms. They are
> > > > releases
> > > > >> completely independently.
> > > > >>
> > > > >> Commit to the "dev" branch always.
> > > > >
> > > > > AND FOREVER!!!!!11!!eleventyone!!!
> > > > >
> > > > > Seriously, can't we have a stable branch instead? Having the dev
> > > > > branch for dev on plugins and having master for dev on platforms is
> > > > > stupid and makes it harder to do work.
> > > >
> > >
> >
>
Re: 3.1 Release
Posted by Michal Mocny <mm...@chromium.org>.
Just to be super duper clear: the reason to work on 'dev' branch of plugins
is not some process decision we are imposing, its a direct requirement
imposed on us by the limitations of our tools (specifically, the state of
the registry as it was with 3.0 launch).
We discussed this in-depth just a week ago (Read "About plugins in 3.1"),
and I think several other times over the last month, if you would like to
read up on the details look there.
No one likes the situation, we've been making headway into fixing it ever
since we discovered the problem, and it can be resolved as soon as users
upgrade from 3.0 (maybe that means we can switch after 3.1 release, maybe
that means we wait for some 3-months deprecation time, not sure).
-Michal
On Tue, Sep 24, 2013 at 9:51 AM, Braden Shepherdson <br...@chromium.org>wrote:
> I agree with Joe that developing on anything other than master sucks. But
> unfortunately, our hands are tied in the near term because the registry
> doesn't know to fetch plugins from anywhere else. Also it makes life easier
> for being who are installing plugins from git URLs.
>
> I think we eventually want to get to a world where 99% of plugin installs
> are happening from the registry, the registry knows how to fetch tags, and
> people who are using git URLs directly know what they're doing and want the
> dev version. (Also you can specify branches with #gitref in the URL, so
> there's flexibility there.) But we're not there yet.
>
> Braden
>
>
> On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com> wrote:
>
> > Yes, let's get this cleared up - confused myself.
> >
> >
> > On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <an...@gmail.com>
> wrote:
> >
> > > 3.1.0 is coincidental and it's temporary for this release because I
> > > wasn't sure where to get the code from and didn't want to compromise
> > > master or dev. I could have called it something else.
> > >
> > > Jesse, I'd advise you to commit to dev. Everything will be merged to
> > > master eventually.
> > >
> > > So to re-iterate the process: right now it's "dev -> master" and
> > > eventually it will be "master -> (independant) plugin version".
> > > amarite?
> > >
> > > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <bo...@gmail.com>
> wrote:
> > > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <agrieve@chromium.org
> >
> > > wrote:
> > > >> Plugins are not tagged nor branched along with platforms. They are
> > > releases
> > > >> completely independently.
> > > >>
> > > >> Commit to the "dev" branch always.
> > > >
> > > > AND FOREVER!!!!!11!!eleventyone!!!
> > > >
> > > > Seriously, can't we have a stable branch instead? Having the dev
> > > > branch for dev on plugins and having master for dev on platforms is
> > > > stupid and makes it harder to do work.
> > >
> >
>
Re: 3.1 Release
Posted by Braden Shepherdson <br...@chromium.org>.
I agree with Joe that developing on anything other than master sucks. But
unfortunately, our hands are tied in the near term because the registry
doesn't know to fetch plugins from anywhere else. Also it makes life easier
for being who are installing plugins from git URLs.
I think we eventually want to get to a world where 99% of plugin installs
are happening from the registry, the registry knows how to fetch tags, and
people who are using git URLs directly know what they're doing and want the
dev version. (Also you can specify branches with #gitref in the URL, so
there's flexibility there.) But we're not there yet.
Braden
On Tue, Sep 24, 2013 at 7:45 AM, Shazron <sh...@gmail.com> wrote:
> Yes, let's get this cleared up - confused myself.
>
>
> On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <an...@gmail.com> wrote:
>
> > 3.1.0 is coincidental and it's temporary for this release because I
> > wasn't sure where to get the code from and didn't want to compromise
> > master or dev. I could have called it something else.
> >
> > Jesse, I'd advise you to commit to dev. Everything will be merged to
> > master eventually.
> >
> > So to re-iterate the process: right now it's "dev -> master" and
> > eventually it will be "master -> (independant) plugin version".
> > amarite?
> >
> > On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <bo...@gmail.com> wrote:
> > > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> > >> Plugins are not tagged nor branched along with platforms. They are
> > releases
> > >> completely independently.
> > >>
> > >> Commit to the "dev" branch always.
> > >
> > > AND FOREVER!!!!!11!!eleventyone!!!
> > >
> > > Seriously, can't we have a stable branch instead? Having the dev
> > > branch for dev on plugins and having master for dev on platforms is
> > > stupid and makes it harder to do work.
> >
>
Re: 3.1 Release
Posted by Shazron <sh...@gmail.com>.
Yes, let's get this cleared up - confused myself.
On Tue, Sep 24, 2013 at 3:52 AM, Anis KADRI <an...@gmail.com> wrote:
> 3.1.0 is coincidental and it's temporary for this release because I
> wasn't sure where to get the code from and didn't want to compromise
> master or dev. I could have called it something else.
>
> Jesse, I'd advise you to commit to dev. Everything will be merged to
> master eventually.
>
> So to re-iterate the process: right now it's "dev -> master" and
> eventually it will be "master -> (independant) plugin version".
> amarite?
>
> On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <bo...@gmail.com> wrote:
> > On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
> >> Plugins are not tagged nor branched along with platforms. They are
> releases
> >> completely independently.
> >>
> >> Commit to the "dev" branch always.
> >
> > AND FOREVER!!!!!11!!eleventyone!!!
> >
> > Seriously, can't we have a stable branch instead? Having the dev
> > branch for dev on plugins and having master for dev on platforms is
> > stupid and makes it harder to do work.
>
Re: 3.1 Release
Posted by Anis KADRI <an...@gmail.com>.
3.1.0 is coincidental and it's temporary for this release because I
wasn't sure where to get the code from and didn't want to compromise
master or dev. I could have called it something else.
Jesse, I'd advise you to commit to dev. Everything will be merged to
master eventually.
So to re-iterate the process: right now it's "dev -> master" and
eventually it will be "master -> (independant) plugin version".
amarite?
On Tue, Sep 24, 2013 at 12:08 AM, Joe Bowser <bo...@gmail.com> wrote:
> On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <ag...@chromium.org> wrote:
>> Plugins are not tagged nor branched along with platforms. They are releases
>> completely independently.
>>
>> Commit to the "dev" branch always.
>
> AND FOREVER!!!!!11!!eleventyone!!!
>
> Seriously, can't we have a stable branch instead? Having the dev
> branch for dev on plugins and having master for dev on platforms is
> stupid and makes it harder to do work.
Re: 3.1 Release
Posted by Joe Bowser <bo...@gmail.com>.
On Mon, Sep 23, 2013 at 2:58 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Plugins are not tagged nor branched along with platforms. They are releases
> completely independently.
>
> Commit to the "dev" branch always.
AND FOREVER!!!!!11!!eleventyone!!!
Seriously, can't we have a stable branch instead? Having the dev
branch for dev on plugins and having master for dev on platforms is
stupid and makes it harder to do work.
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Plugins are not tagged nor branched along with platforms. They are releases
completely independently.
Commit to the "dev" branch always.
For how to do a plugin release (aka merge dev into master, see
https://wiki.apache.org/cordova/StepsForPluginRelease). Anis just added a
branch for pushing them to the cordova registry, where the only difference
is removing the url= attribute from <dependency> tags. That step should be
added to the release page.
On Mon, Sep 23, 2013 at 4:37 PM, Jesse <pu...@gmail.com> wrote:
> I have a small change for Windows 8 that I need to apply to all the core
> plugins.
> Which branch should I work from, and which should I push to?
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Sep 23, 2013 at 9:39 AM, Joe Bowser <bo...@gmail.com> wrote:
>
> > So, what are the plugins being versioned at? 3.x? 1.x?
> >
> > I'm asking because the plugins are tagged with the 3.0.0 release, so
> > it makes sense for them to start there.
> >
> > On Mon, Sep 23, 2013 at 6:40 AM, Braden Shepherdson <braden@chromium.org
> >
> > wrote:
> > > I don't think we want the Cordova version (3.1.0) getting tagged in
> > > plugins. I should think we should merge dev to master and then tag it
> > with
> > > the plugin's own version number, not Cordova versions. Put another way,
> > > it's only a coincidence that this plugin release happens to be near the
> > > Cordova 3.1.0 release.
> > >
> > > Braden
> > >
> > >
> > > On Sat, Sep 21, 2013 at 7:01 AM, Anis KADRI <an...@gmail.com>
> > wrote:
> > >
> > >> Jira issue is: https://issues.apache.org/jira/browse/CB-4889
> > >>
> > >> On Sat, Sep 21, 2013 at 12:59 PM, Anis KADRI <an...@gmail.com>
> > wrote:
> > >> > This is what I've done. Hopefully I didn't mess up because I haven't
> > >> > really followed the master/dev debate.
> > >> >
> > >> > For each plugin:
> > >> > - I created a branch and named it 3.1.0
> > >> > - I pulled from origin dev
> > >> > - I renamed the id from org.apache.cordova.core.* to
> > org.apache.cordova.*
> > >> > - I renamed the version from x.x.xdev to x.x.x
> > >> > - I changed the dependency from URL to id where applicable (I
> believe
> > >> > it was only file-transfer and media-capture)
> > >> > - I published the plugin to the registry
> > >> > - I unpublished the old plugin from the registry.
> > >> >
> > >> > The docs were actually already reflecting IDs without 'core' in them
> > >> > so I didn't update them.
> > >> >
> > >> > The process (once we figure out what to do about those 3.0.0 users)
> > >> > should be in the future.
> > >> > - Work on master
> > >> > - Tag version
> > >> > - Publish that version
> > >> >
> > >> > I left master untouched for all plugins so 3.0.0 users should not
> have
> > >> > any issues.
> > >> >
> > >> > -a
> > >> >
> > >> > On Sat, Sep 21, 2013 at 4:01 AM, Andrew Grieve <
> agrieve@chromium.org>
> > >> wrote:
> > >> >> Sorry for being silent today. I ended up not having much time to
> work
> > >> today
> > >> >> :(. Mostly what I got done is more thinking about how to go about
> > >> things :P.
> > >> >>
> > >> >> That said, Braden did manage to take care of RC1 of CLI! Thanks
> > Braden!
> > >> (
> > >> >> https://issues.apache.org/jira/browse/CB-4837). To get it:
> > >> >>
> > >> >> npm install -g cordova@3.0.10
> > >> >>
> > >> >> With the RC, doing a "cordova platform add" will add the rc1
> > platform,
> > >> and
> > >> >> doing a "cordova platform update" will update an existing platform
> to
> > >> rc1.
> > >> >>
> > >> >> I think we should hold off on a blog post for it until we update
> the
> > >> >> plugins in the registry (and at the same time remove the .core
> > part). If
> > >> >> someone else wants to take that on, that'd be awesome. Otherwise I
> > will
> > >> get
> > >> >> to it on Sunday while I'm in Amsterdam :).
> > >> >>
> > >> >> One revelation I had about the registry:
> > >> >> I think we should *not* remove the url= line from FileTransfer's
> > >> >> <dependency> tag for a little while. This will mean that even when
> > >> >> FileTransfer comes from the registry, its dependency will come
> > straight
> > >> >> from the URL. The copy in the registry and the copy in git are the
> > >> same, so
> > >> >> this should be fine. If we *did* remove the url right away, then
> > people
> > >> >> using the 3.0 tools and following the 3.0 instructions would break.
> > >> >>
> > >> >> New New timeline:
> > >> >> ASAP - Upload rc1 of cordova-docs
> > >> >> Sunday/Monday - Plugin release + Uploading plugins to registry
> > >> >> Monday - Blog post announcing RC1
> > >> >> Rest of week: Test upgrade process, Test the registry out, Make
> sure
> > >> docs
> > >> >> are good, Test download tracking of the registry
> > >> >> Following Monday (ish): Final Release
> > >> >>
> > >> >> In this revision, I push back the final release even more because I
> > >> realize
> > >> >> many of us will be travelling back from AMS.
> > >> >>
> > >> >> On Fri, Sep 20, 2013 at 4:49 PM, Ryan Stewart <rs...@adobe.com>
> > >> wrote:
> > >> >>
> > >> >>> Ahh, thanks for the info. Any ETA on the updated plugins?
> > >> >>>
> > >> >>> =Ryan
> > >> >>>
> > >> >>> On 9/20/13 1:46 PM, "Michal Mocny" <mm...@chromium.org> wrote:
> > >> >>>
> > >> >>> >I think Braden is supposed to get an RC of the cli out today.
> I'm
> > >> told
> > >> >>> >this this may not included updated plugins yet until later,
> though.
> > >> >>> >
> > >> >>> >
> > >> >>> >On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <
> rstewart@adobe.com>
> > >> wrote:
> > >> >>> >
> > >> >>> >> Is the RC still on track to get tagged today?
> > >> >>> >>
> > >> >>> >> I'm working on the PhoneGap-CLI and want to also release an RC
> > >> version
> > >> >>> >>of
> > >> >>> >> that when you guys have tagged.
> > >> >>> >>
> > >> >>> >> =Ryan
> > >> >>> >>
> > >> >>> >> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com>
> > wrote:
> > >> >>> >>
> > >> >>> >> >I think since it has taken longer than expected to get the RC
> > >> tagged,
> > >> >>> >>the
> > >> >>> >> >final release has been push till thursday to allow more time
> to
> > >> test.
> > >> >>> >>Is
> > >> >>> >> >this correct?
> > >> >>> >> >
> > >> >>> >> >
> > >> >>> >> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <
> > >> cmarcelk@gmail.com>
> > >> >>> >> >wrote:
> > >> >>> >> >
> > >> >>> >> >> I'm confused about the date for 3.1.0 final release. These
> two
> > >> posts
> > >> >>> >> >>don't
> > >> >>> >> >> match.
> > >> >>> >> >>
> > >> >>> >> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <
> > >> agrieve@chromium.org>
> > >> >>> >> >>wrote:
> > >> >>> >> >>
> > >> >>> >> >> > Next Thursday:
> > >> >>> >> >> > - If everything seems fine with RC1, release 3.1.0 final.
> > >> >>> >> >> >
> > >> >>> >> >>
> > >> >>> >> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <
> > agrieve@chromium.org
> > >> >
> > >> >>> >> wrote:
> > >> >>> >> >>
> > >> >>> >> >> > Monday 16th - Create release branches & tag RC of all
> repos
> > >> >>> >> >> > Tuesday 17th - Draft Release Blog Post (digest of
> > changelogs)
> > >> >>> >> >> > Monday 20th - Tag 3.1.0 for all repos
> > >> >>> >> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog
> > post
> > >> >>> >> >>
> > >> >>> >> >>
> > >> >>> >> >>
> > >> >>> >>
> > >> >>> >>
> > >> >>>
> > >> >>>
> > >>
> >
>
Re: 3.1 Release
Posted by Jesse <pu...@gmail.com>.
I have a small change for Windows 8 that I need to apply to all the core
plugins.
Which branch should I work from, and which should I push to?
@purplecabbage
risingj.com
On Mon, Sep 23, 2013 at 9:39 AM, Joe Bowser <bo...@gmail.com> wrote:
> So, what are the plugins being versioned at? 3.x? 1.x?
>
> I'm asking because the plugins are tagged with the 3.0.0 release, so
> it makes sense for them to start there.
>
> On Mon, Sep 23, 2013 at 6:40 AM, Braden Shepherdson <br...@chromium.org>
> wrote:
> > I don't think we want the Cordova version (3.1.0) getting tagged in
> > plugins. I should think we should merge dev to master and then tag it
> with
> > the plugin's own version number, not Cordova versions. Put another way,
> > it's only a coincidence that this plugin release happens to be near the
> > Cordova 3.1.0 release.
> >
> > Braden
> >
> >
> > On Sat, Sep 21, 2013 at 7:01 AM, Anis KADRI <an...@gmail.com>
> wrote:
> >
> >> Jira issue is: https://issues.apache.org/jira/browse/CB-4889
> >>
> >> On Sat, Sep 21, 2013 at 12:59 PM, Anis KADRI <an...@gmail.com>
> wrote:
> >> > This is what I've done. Hopefully I didn't mess up because I haven't
> >> > really followed the master/dev debate.
> >> >
> >> > For each plugin:
> >> > - I created a branch and named it 3.1.0
> >> > - I pulled from origin dev
> >> > - I renamed the id from org.apache.cordova.core.* to
> org.apache.cordova.*
> >> > - I renamed the version from x.x.xdev to x.x.x
> >> > - I changed the dependency from URL to id where applicable (I believe
> >> > it was only file-transfer and media-capture)
> >> > - I published the plugin to the registry
> >> > - I unpublished the old plugin from the registry.
> >> >
> >> > The docs were actually already reflecting IDs without 'core' in them
> >> > so I didn't update them.
> >> >
> >> > The process (once we figure out what to do about those 3.0.0 users)
> >> > should be in the future.
> >> > - Work on master
> >> > - Tag version
> >> > - Publish that version
> >> >
> >> > I left master untouched for all plugins so 3.0.0 users should not have
> >> > any issues.
> >> >
> >> > -a
> >> >
> >> > On Sat, Sep 21, 2013 at 4:01 AM, Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >> >> Sorry for being silent today. I ended up not having much time to work
> >> today
> >> >> :(. Mostly what I got done is more thinking about how to go about
> >> things :P.
> >> >>
> >> >> That said, Braden did manage to take care of RC1 of CLI! Thanks
> Braden!
> >> (
> >> >> https://issues.apache.org/jira/browse/CB-4837). To get it:
> >> >>
> >> >> npm install -g cordova@3.0.10
> >> >>
> >> >> With the RC, doing a "cordova platform add" will add the rc1
> platform,
> >> and
> >> >> doing a "cordova platform update" will update an existing platform to
> >> rc1.
> >> >>
> >> >> I think we should hold off on a blog post for it until we update the
> >> >> plugins in the registry (and at the same time remove the .core
> part). If
> >> >> someone else wants to take that on, that'd be awesome. Otherwise I
> will
> >> get
> >> >> to it on Sunday while I'm in Amsterdam :).
> >> >>
> >> >> One revelation I had about the registry:
> >> >> I think we should *not* remove the url= line from FileTransfer's
> >> >> <dependency> tag for a little while. This will mean that even when
> >> >> FileTransfer comes from the registry, its dependency will come
> straight
> >> >> from the URL. The copy in the registry and the copy in git are the
> >> same, so
> >> >> this should be fine. If we *did* remove the url right away, then
> people
> >> >> using the 3.0 tools and following the 3.0 instructions would break.
> >> >>
> >> >> New New timeline:
> >> >> ASAP - Upload rc1 of cordova-docs
> >> >> Sunday/Monday - Plugin release + Uploading plugins to registry
> >> >> Monday - Blog post announcing RC1
> >> >> Rest of week: Test upgrade process, Test the registry out, Make sure
> >> docs
> >> >> are good, Test download tracking of the registry
> >> >> Following Monday (ish): Final Release
> >> >>
> >> >> In this revision, I push back the final release even more because I
> >> realize
> >> >> many of us will be travelling back from AMS.
> >> >>
> >> >> On Fri, Sep 20, 2013 at 4:49 PM, Ryan Stewart <rs...@adobe.com>
> >> wrote:
> >> >>
> >> >>> Ahh, thanks for the info. Any ETA on the updated plugins?
> >> >>>
> >> >>> =Ryan
> >> >>>
> >> >>> On 9/20/13 1:46 PM, "Michal Mocny" <mm...@chromium.org> wrote:
> >> >>>
> >> >>> >I think Braden is supposed to get an RC of the cli out today. I'm
> >> told
> >> >>> >this this may not included updated plugins yet until later, though.
> >> >>> >
> >> >>> >
> >> >>> >On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <rs...@adobe.com>
> >> wrote:
> >> >>> >
> >> >>> >> Is the RC still on track to get tagged today?
> >> >>> >>
> >> >>> >> I'm working on the PhoneGap-CLI and want to also release an RC
> >> version
> >> >>> >>of
> >> >>> >> that when you guys have tagged.
> >> >>> >>
> >> >>> >> =Ryan
> >> >>> >>
> >> >>> >> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com>
> wrote:
> >> >>> >>
> >> >>> >> >I think since it has taken longer than expected to get the RC
> >> tagged,
> >> >>> >>the
> >> >>> >> >final release has been push till thursday to allow more time to
> >> test.
> >> >>> >>Is
> >> >>> >> >this correct?
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <
> >> cmarcelk@gmail.com>
> >> >>> >> >wrote:
> >> >>> >> >
> >> >>> >> >> I'm confused about the date for 3.1.0 final release. These two
> >> posts
> >> >>> >> >>don't
> >> >>> >> >> match.
> >> >>> >> >>
> >> >>> >> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <
> >> agrieve@chromium.org>
> >> >>> >> >>wrote:
> >> >>> >> >>
> >> >>> >> >> > Next Thursday:
> >> >>> >> >> > - If everything seems fine with RC1, release 3.1.0 final.
> >> >>> >> >> >
> >> >>> >> >>
> >> >>> >> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <
> agrieve@chromium.org
> >> >
> >> >>> >> wrote:
> >> >>> >> >>
> >> >>> >> >> > Monday 16th - Create release branches & tag RC of all repos
> >> >>> >> >> > Tuesday 17th - Draft Release Blog Post (digest of
> changelogs)
> >> >>> >> >> > Monday 20th - Tag 3.1.0 for all repos
> >> >>> >> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog
> post
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >>
> >> >>> >>
> >> >>>
> >> >>>
> >>
>
Re: 3.1 Release
Posted by Joe Bowser <bo...@gmail.com>.
So, what are the plugins being versioned at? 3.x? 1.x?
I'm asking because the plugins are tagged with the 3.0.0 release, so
it makes sense for them to start there.
On Mon, Sep 23, 2013 at 6:40 AM, Braden Shepherdson <br...@chromium.org> wrote:
> I don't think we want the Cordova version (3.1.0) getting tagged in
> plugins. I should think we should merge dev to master and then tag it with
> the plugin's own version number, not Cordova versions. Put another way,
> it's only a coincidence that this plugin release happens to be near the
> Cordova 3.1.0 release.
>
> Braden
>
>
> On Sat, Sep 21, 2013 at 7:01 AM, Anis KADRI <an...@gmail.com> wrote:
>
>> Jira issue is: https://issues.apache.org/jira/browse/CB-4889
>>
>> On Sat, Sep 21, 2013 at 12:59 PM, Anis KADRI <an...@gmail.com> wrote:
>> > This is what I've done. Hopefully I didn't mess up because I haven't
>> > really followed the master/dev debate.
>> >
>> > For each plugin:
>> > - I created a branch and named it 3.1.0
>> > - I pulled from origin dev
>> > - I renamed the id from org.apache.cordova.core.* to org.apache.cordova.*
>> > - I renamed the version from x.x.xdev to x.x.x
>> > - I changed the dependency from URL to id where applicable (I believe
>> > it was only file-transfer and media-capture)
>> > - I published the plugin to the registry
>> > - I unpublished the old plugin from the registry.
>> >
>> > The docs were actually already reflecting IDs without 'core' in them
>> > so I didn't update them.
>> >
>> > The process (once we figure out what to do about those 3.0.0 users)
>> > should be in the future.
>> > - Work on master
>> > - Tag version
>> > - Publish that version
>> >
>> > I left master untouched for all plugins so 3.0.0 users should not have
>> > any issues.
>> >
>> > -a
>> >
>> > On Sat, Sep 21, 2013 at 4:01 AM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>> >> Sorry for being silent today. I ended up not having much time to work
>> today
>> >> :(. Mostly what I got done is more thinking about how to go about
>> things :P.
>> >>
>> >> That said, Braden did manage to take care of RC1 of CLI! Thanks Braden!
>> (
>> >> https://issues.apache.org/jira/browse/CB-4837). To get it:
>> >>
>> >> npm install -g cordova@3.0.10
>> >>
>> >> With the RC, doing a "cordova platform add" will add the rc1 platform,
>> and
>> >> doing a "cordova platform update" will update an existing platform to
>> rc1.
>> >>
>> >> I think we should hold off on a blog post for it until we update the
>> >> plugins in the registry (and at the same time remove the .core part). If
>> >> someone else wants to take that on, that'd be awesome. Otherwise I will
>> get
>> >> to it on Sunday while I'm in Amsterdam :).
>> >>
>> >> One revelation I had about the registry:
>> >> I think we should *not* remove the url= line from FileTransfer's
>> >> <dependency> tag for a little while. This will mean that even when
>> >> FileTransfer comes from the registry, its dependency will come straight
>> >> from the URL. The copy in the registry and the copy in git are the
>> same, so
>> >> this should be fine. If we *did* remove the url right away, then people
>> >> using the 3.0 tools and following the 3.0 instructions would break.
>> >>
>> >> New New timeline:
>> >> ASAP - Upload rc1 of cordova-docs
>> >> Sunday/Monday - Plugin release + Uploading plugins to registry
>> >> Monday - Blog post announcing RC1
>> >> Rest of week: Test upgrade process, Test the registry out, Make sure
>> docs
>> >> are good, Test download tracking of the registry
>> >> Following Monday (ish): Final Release
>> >>
>> >> In this revision, I push back the final release even more because I
>> realize
>> >> many of us will be travelling back from AMS.
>> >>
>> >> On Fri, Sep 20, 2013 at 4:49 PM, Ryan Stewart <rs...@adobe.com>
>> wrote:
>> >>
>> >>> Ahh, thanks for the info. Any ETA on the updated plugins?
>> >>>
>> >>> =Ryan
>> >>>
>> >>> On 9/20/13 1:46 PM, "Michal Mocny" <mm...@chromium.org> wrote:
>> >>>
>> >>> >I think Braden is supposed to get an RC of the cli out today. I'm
>> told
>> >>> >this this may not included updated plugins yet until later, though.
>> >>> >
>> >>> >
>> >>> >On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <rs...@adobe.com>
>> wrote:
>> >>> >
>> >>> >> Is the RC still on track to get tagged today?
>> >>> >>
>> >>> >> I'm working on the PhoneGap-CLI and want to also release an RC
>> version
>> >>> >>of
>> >>> >> that when you guys have tagged.
>> >>> >>
>> >>> >> =Ryan
>> >>> >>
>> >>> >> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com> wrote:
>> >>> >>
>> >>> >> >I think since it has taken longer than expected to get the RC
>> tagged,
>> >>> >>the
>> >>> >> >final release has been push till thursday to allow more time to
>> test.
>> >>> >>Is
>> >>> >> >this correct?
>> >>> >> >
>> >>> >> >
>> >>> >> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <
>> cmarcelk@gmail.com>
>> >>> >> >wrote:
>> >>> >> >
>> >>> >> >> I'm confused about the date for 3.1.0 final release. These two
>> posts
>> >>> >> >>don't
>> >>> >> >> match.
>> >>> >> >>
>> >>> >> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <
>> agrieve@chromium.org>
>> >>> >> >>wrote:
>> >>> >> >>
>> >>> >> >> > Next Thursday:
>> >>> >> >> > - If everything seems fine with RC1, release 3.1.0 final.
>> >>> >> >> >
>> >>> >> >>
>> >>> >> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <agrieve@chromium.org
>> >
>> >>> >> wrote:
>> >>> >> >>
>> >>> >> >> > Monday 16th - Create release branches & tag RC of all repos
>> >>> >> >> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>> >>> >> >> > Monday 20th - Tag 3.1.0 for all repos
>> >>> >> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >>
>> >>> >>
>> >>>
>> >>>
>>
Re: 3.1 Release
Posted by Braden Shepherdson <br...@chromium.org>.
I don't think we want the Cordova version (3.1.0) getting tagged in
plugins. I should think we should merge dev to master and then tag it with
the plugin's own version number, not Cordova versions. Put another way,
it's only a coincidence that this plugin release happens to be near the
Cordova 3.1.0 release.
Braden
On Sat, Sep 21, 2013 at 7:01 AM, Anis KADRI <an...@gmail.com> wrote:
> Jira issue is: https://issues.apache.org/jira/browse/CB-4889
>
> On Sat, Sep 21, 2013 at 12:59 PM, Anis KADRI <an...@gmail.com> wrote:
> > This is what I've done. Hopefully I didn't mess up because I haven't
> > really followed the master/dev debate.
> >
> > For each plugin:
> > - I created a branch and named it 3.1.0
> > - I pulled from origin dev
> > - I renamed the id from org.apache.cordova.core.* to org.apache.cordova.*
> > - I renamed the version from x.x.xdev to x.x.x
> > - I changed the dependency from URL to id where applicable (I believe
> > it was only file-transfer and media-capture)
> > - I published the plugin to the registry
> > - I unpublished the old plugin from the registry.
> >
> > The docs were actually already reflecting IDs without 'core' in them
> > so I didn't update them.
> >
> > The process (once we figure out what to do about those 3.0.0 users)
> > should be in the future.
> > - Work on master
> > - Tag version
> > - Publish that version
> >
> > I left master untouched for all plugins so 3.0.0 users should not have
> > any issues.
> >
> > -a
> >
> > On Sat, Sep 21, 2013 at 4:01 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
> >> Sorry for being silent today. I ended up not having much time to work
> today
> >> :(. Mostly what I got done is more thinking about how to go about
> things :P.
> >>
> >> That said, Braden did manage to take care of RC1 of CLI! Thanks Braden!
> (
> >> https://issues.apache.org/jira/browse/CB-4837). To get it:
> >>
> >> npm install -g cordova@3.0.10
> >>
> >> With the RC, doing a "cordova platform add" will add the rc1 platform,
> and
> >> doing a "cordova platform update" will update an existing platform to
> rc1.
> >>
> >> I think we should hold off on a blog post for it until we update the
> >> plugins in the registry (and at the same time remove the .core part). If
> >> someone else wants to take that on, that'd be awesome. Otherwise I will
> get
> >> to it on Sunday while I'm in Amsterdam :).
> >>
> >> One revelation I had about the registry:
> >> I think we should *not* remove the url= line from FileTransfer's
> >> <dependency> tag for a little while. This will mean that even when
> >> FileTransfer comes from the registry, its dependency will come straight
> >> from the URL. The copy in the registry and the copy in git are the
> same, so
> >> this should be fine. If we *did* remove the url right away, then people
> >> using the 3.0 tools and following the 3.0 instructions would break.
> >>
> >> New New timeline:
> >> ASAP - Upload rc1 of cordova-docs
> >> Sunday/Monday - Plugin release + Uploading plugins to registry
> >> Monday - Blog post announcing RC1
> >> Rest of week: Test upgrade process, Test the registry out, Make sure
> docs
> >> are good, Test download tracking of the registry
> >> Following Monday (ish): Final Release
> >>
> >> In this revision, I push back the final release even more because I
> realize
> >> many of us will be travelling back from AMS.
> >>
> >> On Fri, Sep 20, 2013 at 4:49 PM, Ryan Stewart <rs...@adobe.com>
> wrote:
> >>
> >>> Ahh, thanks for the info. Any ETA on the updated plugins?
> >>>
> >>> =Ryan
> >>>
> >>> On 9/20/13 1:46 PM, "Michal Mocny" <mm...@chromium.org> wrote:
> >>>
> >>> >I think Braden is supposed to get an RC of the cli out today. I'm
> told
> >>> >this this may not included updated plugins yet until later, though.
> >>> >
> >>> >
> >>> >On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <rs...@adobe.com>
> wrote:
> >>> >
> >>> >> Is the RC still on track to get tagged today?
> >>> >>
> >>> >> I'm working on the PhoneGap-CLI and want to also release an RC
> version
> >>> >>of
> >>> >> that when you guys have tagged.
> >>> >>
> >>> >> =Ryan
> >>> >>
> >>> >> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com> wrote:
> >>> >>
> >>> >> >I think since it has taken longer than expected to get the RC
> tagged,
> >>> >>the
> >>> >> >final release has been push till thursday to allow more time to
> test.
> >>> >>Is
> >>> >> >this correct?
> >>> >> >
> >>> >> >
> >>> >> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <
> cmarcelk@gmail.com>
> >>> >> >wrote:
> >>> >> >
> >>> >> >> I'm confused about the date for 3.1.0 final release. These two
> posts
> >>> >> >>don't
> >>> >> >> match.
> >>> >> >>
> >>> >> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <
> agrieve@chromium.org>
> >>> >> >>wrote:
> >>> >> >>
> >>> >> >> > Next Thursday:
> >>> >> >> > - If everything seems fine with RC1, release 3.1.0 final.
> >>> >> >> >
> >>> >> >>
> >>> >> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <agrieve@chromium.org
> >
> >>> >> wrote:
> >>> >> >>
> >>> >> >> > Monday 16th - Create release branches & tag RC of all repos
> >>> >> >> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> >>> >> >> > Monday 20th - Tag 3.1.0 for all repos
> >>> >> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >>
> >>> >>
> >>>
> >>>
>
Re: 3.1 Release
Posted by Anis KADRI <an...@gmail.com>.
Jira issue is: https://issues.apache.org/jira/browse/CB-4889
On Sat, Sep 21, 2013 at 12:59 PM, Anis KADRI <an...@gmail.com> wrote:
> This is what I've done. Hopefully I didn't mess up because I haven't
> really followed the master/dev debate.
>
> For each plugin:
> - I created a branch and named it 3.1.0
> - I pulled from origin dev
> - I renamed the id from org.apache.cordova.core.* to org.apache.cordova.*
> - I renamed the version from x.x.xdev to x.x.x
> - I changed the dependency from URL to id where applicable (I believe
> it was only file-transfer and media-capture)
> - I published the plugin to the registry
> - I unpublished the old plugin from the registry.
>
> The docs were actually already reflecting IDs without 'core' in them
> so I didn't update them.
>
> The process (once we figure out what to do about those 3.0.0 users)
> should be in the future.
> - Work on master
> - Tag version
> - Publish that version
>
> I left master untouched for all plugins so 3.0.0 users should not have
> any issues.
>
> -a
>
> On Sat, Sep 21, 2013 at 4:01 AM, Andrew Grieve <ag...@chromium.org> wrote:
>> Sorry for being silent today. I ended up not having much time to work today
>> :(. Mostly what I got done is more thinking about how to go about things :P.
>>
>> That said, Braden did manage to take care of RC1 of CLI! Thanks Braden! (
>> https://issues.apache.org/jira/browse/CB-4837). To get it:
>>
>> npm install -g cordova@3.0.10
>>
>> With the RC, doing a "cordova platform add" will add the rc1 platform, and
>> doing a "cordova platform update" will update an existing platform to rc1.
>>
>> I think we should hold off on a blog post for it until we update the
>> plugins in the registry (and at the same time remove the .core part). If
>> someone else wants to take that on, that'd be awesome. Otherwise I will get
>> to it on Sunday while I'm in Amsterdam :).
>>
>> One revelation I had about the registry:
>> I think we should *not* remove the url= line from FileTransfer's
>> <dependency> tag for a little while. This will mean that even when
>> FileTransfer comes from the registry, its dependency will come straight
>> from the URL. The copy in the registry and the copy in git are the same, so
>> this should be fine. If we *did* remove the url right away, then people
>> using the 3.0 tools and following the 3.0 instructions would break.
>>
>> New New timeline:
>> ASAP - Upload rc1 of cordova-docs
>> Sunday/Monday - Plugin release + Uploading plugins to registry
>> Monday - Blog post announcing RC1
>> Rest of week: Test upgrade process, Test the registry out, Make sure docs
>> are good, Test download tracking of the registry
>> Following Monday (ish): Final Release
>>
>> In this revision, I push back the final release even more because I realize
>> many of us will be travelling back from AMS.
>>
>> On Fri, Sep 20, 2013 at 4:49 PM, Ryan Stewart <rs...@adobe.com> wrote:
>>
>>> Ahh, thanks for the info. Any ETA on the updated plugins?
>>>
>>> =Ryan
>>>
>>> On 9/20/13 1:46 PM, "Michal Mocny" <mm...@chromium.org> wrote:
>>>
>>> >I think Braden is supposed to get an RC of the cli out today. I'm told
>>> >this this may not included updated plugins yet until later, though.
>>> >
>>> >
>>> >On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <rs...@adobe.com> wrote:
>>> >
>>> >> Is the RC still on track to get tagged today?
>>> >>
>>> >> I'm working on the PhoneGap-CLI and want to also release an RC version
>>> >>of
>>> >> that when you guys have tagged.
>>> >>
>>> >> =Ryan
>>> >>
>>> >> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com> wrote:
>>> >>
>>> >> >I think since it has taken longer than expected to get the RC tagged,
>>> >>the
>>> >> >final release has been push till thursday to allow more time to test.
>>> >>Is
>>> >> >this correct?
>>> >> >
>>> >> >
>>> >> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <cm...@gmail.com>
>>> >> >wrote:
>>> >> >
>>> >> >> I'm confused about the date for 3.1.0 final release. These two posts
>>> >> >>don't
>>> >> >> match.
>>> >> >>
>>> >> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <ag...@chromium.org>
>>> >> >>wrote:
>>> >> >>
>>> >> >> > Next Thursday:
>>> >> >> > - If everything seems fine with RC1, release 3.1.0 final.
>>> >> >> >
>>> >> >>
>>> >> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <ag...@chromium.org>
>>> >> wrote:
>>> >> >>
>>> >> >> > Monday 16th - Create release branches & tag RC of all repos
>>> >> >> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>>> >> >> > Monday 20th - Tag 3.1.0 for all repos
>>> >> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>> >> >>
>>> >> >>
>>> >> >>
>>> >>
>>> >>
>>>
>>>
Re: 3.1 Release
Posted by Anis KADRI <an...@gmail.com>.
This is what I've done. Hopefully I didn't mess up because I haven't
really followed the master/dev debate.
For each plugin:
- I created a branch and named it 3.1.0
- I pulled from origin dev
- I renamed the id from org.apache.cordova.core.* to org.apache.cordova.*
- I renamed the version from x.x.xdev to x.x.x
- I changed the dependency from URL to id where applicable (I believe
it was only file-transfer and media-capture)
- I published the plugin to the registry
- I unpublished the old plugin from the registry.
The docs were actually already reflecting IDs without 'core' in them
so I didn't update them.
The process (once we figure out what to do about those 3.0.0 users)
should be in the future.
- Work on master
- Tag version
- Publish that version
I left master untouched for all plugins so 3.0.0 users should not have
any issues.
-a
On Sat, Sep 21, 2013 at 4:01 AM, Andrew Grieve <ag...@chromium.org> wrote:
> Sorry for being silent today. I ended up not having much time to work today
> :(. Mostly what I got done is more thinking about how to go about things :P.
>
> That said, Braden did manage to take care of RC1 of CLI! Thanks Braden! (
> https://issues.apache.org/jira/browse/CB-4837). To get it:
>
> npm install -g cordova@3.0.10
>
> With the RC, doing a "cordova platform add" will add the rc1 platform, and
> doing a "cordova platform update" will update an existing platform to rc1.
>
> I think we should hold off on a blog post for it until we update the
> plugins in the registry (and at the same time remove the .core part). If
> someone else wants to take that on, that'd be awesome. Otherwise I will get
> to it on Sunday while I'm in Amsterdam :).
>
> One revelation I had about the registry:
> I think we should *not* remove the url= line from FileTransfer's
> <dependency> tag for a little while. This will mean that even when
> FileTransfer comes from the registry, its dependency will come straight
> from the URL. The copy in the registry and the copy in git are the same, so
> this should be fine. If we *did* remove the url right away, then people
> using the 3.0 tools and following the 3.0 instructions would break.
>
> New New timeline:
> ASAP - Upload rc1 of cordova-docs
> Sunday/Monday - Plugin release + Uploading plugins to registry
> Monday - Blog post announcing RC1
> Rest of week: Test upgrade process, Test the registry out, Make sure docs
> are good, Test download tracking of the registry
> Following Monday (ish): Final Release
>
> In this revision, I push back the final release even more because I realize
> many of us will be travelling back from AMS.
>
> On Fri, Sep 20, 2013 at 4:49 PM, Ryan Stewart <rs...@adobe.com> wrote:
>
>> Ahh, thanks for the info. Any ETA on the updated plugins?
>>
>> =Ryan
>>
>> On 9/20/13 1:46 PM, "Michal Mocny" <mm...@chromium.org> wrote:
>>
>> >I think Braden is supposed to get an RC of the cli out today. I'm told
>> >this this may not included updated plugins yet until later, though.
>> >
>> >
>> >On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <rs...@adobe.com> wrote:
>> >
>> >> Is the RC still on track to get tagged today?
>> >>
>> >> I'm working on the PhoneGap-CLI and want to also release an RC version
>> >>of
>> >> that when you guys have tagged.
>> >>
>> >> =Ryan
>> >>
>> >> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com> wrote:
>> >>
>> >> >I think since it has taken longer than expected to get the RC tagged,
>> >>the
>> >> >final release has been push till thursday to allow more time to test.
>> >>Is
>> >> >this correct?
>> >> >
>> >> >
>> >> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <cm...@gmail.com>
>> >> >wrote:
>> >> >
>> >> >> I'm confused about the date for 3.1.0 final release. These two posts
>> >> >>don't
>> >> >> match.
>> >> >>
>> >> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <ag...@chromium.org>
>> >> >>wrote:
>> >> >>
>> >> >> > Next Thursday:
>> >> >> > - If everything seems fine with RC1, release 3.1.0 final.
>> >> >> >
>> >> >>
>> >> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <ag...@chromium.org>
>> >> wrote:
>> >> >>
>> >> >> > Monday 16th - Create release branches & tag RC of all repos
>> >> >> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>> >> >> > Monday 20th - Tag 3.1.0 for all repos
>> >> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Sorry for being silent today. I ended up not having much time to work today
:(. Mostly what I got done is more thinking about how to go about things :P.
That said, Braden did manage to take care of RC1 of CLI! Thanks Braden! (
https://issues.apache.org/jira/browse/CB-4837). To get it:
npm install -g cordova@3.0.10
With the RC, doing a "cordova platform add" will add the rc1 platform, and
doing a "cordova platform update" will update an existing platform to rc1.
I think we should hold off on a blog post for it until we update the
plugins in the registry (and at the same time remove the .core part). If
someone else wants to take that on, that'd be awesome. Otherwise I will get
to it on Sunday while I'm in Amsterdam :).
One revelation I had about the registry:
I think we should *not* remove the url= line from FileTransfer's
<dependency> tag for a little while. This will mean that even when
FileTransfer comes from the registry, its dependency will come straight
from the URL. The copy in the registry and the copy in git are the same, so
this should be fine. If we *did* remove the url right away, then people
using the 3.0 tools and following the 3.0 instructions would break.
New New timeline:
ASAP - Upload rc1 of cordova-docs
Sunday/Monday - Plugin release + Uploading plugins to registry
Monday - Blog post announcing RC1
Rest of week: Test upgrade process, Test the registry out, Make sure docs
are good, Test download tracking of the registry
Following Monday (ish): Final Release
In this revision, I push back the final release even more because I realize
many of us will be travelling back from AMS.
On Fri, Sep 20, 2013 at 4:49 PM, Ryan Stewart <rs...@adobe.com> wrote:
> Ahh, thanks for the info. Any ETA on the updated plugins?
>
> =Ryan
>
> On 9/20/13 1:46 PM, "Michal Mocny" <mm...@chromium.org> wrote:
>
> >I think Braden is supposed to get an RC of the cli out today. I'm told
> >this this may not included updated plugins yet until later, though.
> >
> >
> >On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <rs...@adobe.com> wrote:
> >
> >> Is the RC still on track to get tagged today?
> >>
> >> I'm working on the PhoneGap-CLI and want to also release an RC version
> >>of
> >> that when you guys have tagged.
> >>
> >> =Ryan
> >>
> >> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com> wrote:
> >>
> >> >I think since it has taken longer than expected to get the RC tagged,
> >>the
> >> >final release has been push till thursday to allow more time to test.
> >>Is
> >> >this correct?
> >> >
> >> >
> >> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <cm...@gmail.com>
> >> >wrote:
> >> >
> >> >> I'm confused about the date for 3.1.0 final release. These two posts
> >> >>don't
> >> >> match.
> >> >>
> >> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <ag...@chromium.org>
> >> >>wrote:
> >> >>
> >> >> > Next Thursday:
> >> >> > - If everything seems fine with RC1, release 3.1.0 final.
> >> >> >
> >> >>
> >> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <ag...@chromium.org>
> >> wrote:
> >> >>
> >> >> > Monday 16th - Create release branches & tag RC of all repos
> >> >> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> >> >> > Monday 20th - Tag 3.1.0 for all repos
> >> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >> >>
> >> >>
> >> >>
> >>
> >>
>
>
Re: 3.1 Release
Posted by Ryan Stewart <rs...@adobe.com>.
Ahh, thanks for the info. Any ETA on the updated plugins?
=Ryan
On 9/20/13 1:46 PM, "Michal Mocny" <mm...@chromium.org> wrote:
>I think Braden is supposed to get an RC of the cli out today. I'm told
>this this may not included updated plugins yet until later, though.
>
>
>On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <rs...@adobe.com> wrote:
>
>> Is the RC still on track to get tagged today?
>>
>> I'm working on the PhoneGap-CLI and want to also release an RC version
>>of
>> that when you guys have tagged.
>>
>> =Ryan
>>
>> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com> wrote:
>>
>> >I think since it has taken longer than expected to get the RC tagged,
>>the
>> >final release has been push till thursday to allow more time to test.
>>Is
>> >this correct?
>> >
>> >
>> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <cm...@gmail.com>
>> >wrote:
>> >
>> >> I'm confused about the date for 3.1.0 final release. These two posts
>> >>don't
>> >> match.
>> >>
>> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <ag...@chromium.org>
>> >>wrote:
>> >>
>> >> > Next Thursday:
>> >> > - If everything seems fine with RC1, release 3.1.0 final.
>> >> >
>> >>
>> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>> >>
>> >> > Monday 16th - Create release branches & tag RC of all repos
>> >> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>> >> > Monday 20th - Tag 3.1.0 for all repos
>> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> >>
>> >>
>> >>
>>
>>
Re: 3.1 Release
Posted by Michal Mocny <mm...@chromium.org>.
I think Braden is supposed to get an RC of the cli out today. I'm told
this this may not included updated plugins yet until later, though.
On Fri, Sep 20, 2013 at 4:19 PM, Ryan Stewart <rs...@adobe.com> wrote:
> Is the RC still on track to get tagged today?
>
> I'm working on the PhoneGap-CLI and want to also release an RC version of
> that when you guys have tagged.
>
> =Ryan
>
> On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com> wrote:
>
> >I think since it has taken longer than expected to get the RC tagged, the
> >final release has been push till thursday to allow more time to test. Is
> >this correct?
> >
> >
> >On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <cm...@gmail.com>
> >wrote:
> >
> >> I'm confused about the date for 3.1.0 final release. These two posts
> >>don't
> >> match.
> >>
> >> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <ag...@chromium.org>
> >>wrote:
> >>
> >> > Next Thursday:
> >> > - If everything seems fine with RC1, release 3.1.0 final.
> >> >
> >>
> >> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
> >>
> >> > Monday 16th - Create release branches & tag RC of all repos
> >> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> >> > Monday 20th - Tag 3.1.0 for all repos
> >> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>
> >>
> >>
>
>
Re: 3.1 Release
Posted by Ryan Stewart <rs...@adobe.com>.
Is the RC still on track to get tagged today?
I'm working on the PhoneGap-CLI and want to also release an RC version of
that when you guys have tagged.
=Ryan
On 9/20/13 1:01 PM, "Steven Gill" <st...@gmail.com> wrote:
>I think since it has taken longer than expected to get the RC tagged, the
>final release has been push till thursday to allow more time to test. Is
>this correct?
>
>
>On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <cm...@gmail.com>
>wrote:
>
>> I'm confused about the date for 3.1.0 final release. These two posts
>>don't
>> match.
>>
>> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <ag...@chromium.org>
>>wrote:
>>
>> > Next Thursday:
>> > - If everything seems fine with RC1, release 3.1.0 final.
>> >
>>
>> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <ag...@chromium.org> wrote:
>>
>> > Monday 16th - Create release branches & tag RC of all repos
>> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
>> > Monday 20th - Tag 3.1.0 for all repos
>> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>
>>
>>
Re: 3.1 Release
Posted by Steven Gill <st...@gmail.com>.
I think since it has taken longer than expected to get the RC tagged, the
final release has been push till thursday to allow more time to test. Is
this correct?
On Fri, Sep 20, 2013 at 12:58 PM, Marcel Kinard <cm...@gmail.com> wrote:
> I'm confused about the date for 3.1.0 final release. These two posts don't
> match.
>
> On Sep 19, 2013, at 11:27 PM, Andrew Grieve <ag...@chromium.org> wrote:
>
> > Next Thursday:
> > - If everything seems fine with RC1, release 3.1.0 final.
> >
>
> On Sep 10, 2013, at 3:20 PM, Andrew Grieve <ag...@chromium.org> wrote:
>
> > Monday 16th - Create release branches & tag RC of all repos
> > Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> > Monday 20th - Tag 3.1.0 for all repos
> > Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>
>
>
Re: 3.1 Release
Posted by Marcel Kinard <cm...@gmail.com>.
I'm confused about the date for 3.1.0 final release. These two posts don't match.
On Sep 19, 2013, at 11:27 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Next Thursday:
> - If everything seems fine with RC1, release 3.1.0 final.
>
On Sep 10, 2013, at 3:20 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Monday 16th - Create release branches & tag RC of all repos
> Tuesday 17th - Draft Release Blog Post (digest of changelogs)
> Monday 20th - Tag 3.1.0 for all repos
> Tuesday 21st - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
Re: 3.1 Release
Posted by Steven Gill <st...@gmail.com>.
Hey Andrew,
Need any help with this stuff? Let me know if you want me to take care some
of these.
-Steve
On Fri, Sep 20, 2013 at 10:52 AM, Andrew Grieve <ag...@chromium.org>wrote:
> Sounds good. I don't think we need a release branch on docs if it's not
> adding benefit.
>
>
> On Fri, Sep 20, 2013 at 4:25 AM, Michael Brooks <michael@michaelbrooks.ca
> >wrote:
>
> > >
> > > Michael: I noticed that the launch bug I created is missing any
> subtasks
> > > for cordova-docs (whoops!). Also - in the current CuttingReleases page,
> > we
> > > don't actually say that the docs branch should be created until once
> > we're
> > > ready to launch final. I think this is wrong, but wanted to know what
> > your
> > > thoughts are for it. I'm thinking:
> > > - cordova-docs should have a release branch created as soon as the RCs
> of
> > > the platforms are tagged
> > > - I don't think there's much value in having an RC tag for the docs,
> > since
> > > they tend to change a bunch post RC1 of platforms
> > > - cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be
> > > made the default. We can keep re-uploading it as changes are made.
> > > - Once we're ready for the final release, we delete the rc1 version,
> > > upload the non-rc version, and make that the default.
> > > Does this sound good?
> >
> >
> > If possible, it would be nice to avoid creating any branches for the
> > cordova-docs. When we have a branch, the maintainers need to apply their
> > commits to both the master and the release branch. It's error prone and
> > troublesome. Since we version cordova-docs by directory, can we skip the
> > release branch without messing up the release process? Of course, this is
> > temproary. When we switch the a new doc generator and restructure the
> docs,
> > we will version by tags and then we can adopt the release branch
> approach.
> >
> > The rest of your steps are exactly how I see it working out.
> >
> >
> > On Thu, Sep 19, 2013 at 8:27 PM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > Sounds good.
> > >
> > > So - here's what I'm thinking for next steps:
> > >
> > > Friday:
> > > - Remove "core" from plugin IDs
> > > - Remove URLs from <dependency> tags
> > > - Do a plugins release
> > > - Do a plugman release
> > > - Do a CLI release, but don't tag it as "latest", tag it as "rc"
> instead.
> > > This will cause it to be installed only if you type "npm install
> > cordova@rc
> > > "
> > > - Add "cordova platform update" instructions to the upgrade guides
> within
> > > the docs
> > > - Upload RC1 of cordova-docs
> > > - Write blog post about the availability of the RC1. Tweet it.
> > >
> > > Next Thursday:
> > > - If everything seems fine with RC1, release 3.1.0 final.
> > >
> > > Sound good?
> > >
> > >
> > > Michael: I noticed that the launch bug I created is missing any
> subtasks
> > > for cordova-docs (whoops!). Also - in the current CuttingReleases page,
> > we
> > > don't actually say that the docs branch should be created until once
> > we're
> > > ready to launch final. I think this is wrong, but wanted to know what
> > your
> > > thoughts are for it. I'm thinking:
> > > - cordova-docs should have a release branch created as soon as the RCs
> of
> > > the platforms are tagged
> > > - I don't think there's much value in having an RC tag for the docs,
> > since
> > > they tend to change a bunch post RC1 of platforms
> > > - cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be
> > > made the default. We can keep re-uploading it as changes are made.
> > > - Once we're ready for the final release, we delete the rc1 version,
> > > upload the non-rc version, and make that the default.
> > >
> > > Does this sound good?
> > >
> > >
> > >
> > > On Thu, Sep 19, 2013 at 11:04 PM, Shazron <sh...@gmail.com> wrote:
> > >
> > >> Lets skip it, it's unchanged
> > >>
> > >> On Thursday, September 19, 2013, Andrew Grieve wrote:
> > >>
> > >> > Thanks Shaz. Do you want to do OSX as well, or should we skip that
> for
> > >> this
> > >> > release?
> > >> >
> > >> >
> > >> > On Thu, Sep 19, 2013 at 8:56 PM, Shazron <sh...@gmail.com> wrote:
> > >> >
> > >> > > ios-deploy stuff a no go so I left it out (check out the issue for
> > the
> > >> > > sordid details) :(
> > >> > >
> > >> > > sorry for the delay, I had other pressing work related stuff.
> > >> > > Tested mob-spec on iOS 7 and iOS 6 - it works fine, iOS tagged.
> Only
> > >> one
> > >> > > failure on iOS 6 - contacts.spec.24.
> > >> > >
> > >> > >
> > >> > > On Thu, Sep 19, 2013 at 10:37 AM, Lorin Beer <
> > >> lorin.beer.dev@gmail.com
> > >> > > >wrote:
> > >> > >
> > >> > > > I was away a good chunk of yesterday due to a sick wife, getting
> > BB
> > >> > > tagged
> > >> > > > today. Sorry for the delay.
> > >> > > >
> > >> > > >
> > >> > > > On Thu, Sep 19, 2013 at 9:59 AM, Shazron <sh...@gmail.com>
> > wrote:
> > >> > > >
> > >> > > > > Sorry for the iOS release guys I'm getting it out today
> > >> > > > >
> > >> > > > >
> > >> > > > > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <
> > >> mmocny@chromium.org>
> > >> > > > wrote:
> > >> > > > >
> > >> > > > > > Specifically, I think the section "Branch & Tag RC1 for
> > Platform
> > >> > > > > > Repositories"
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <
> > >> mmocny@chromium.org
> > >> > >
> > >> > > > > wrote:
> > >> > > > > >
> > >> > > > > > > I think its this one:
> > >> > > http://wiki.apache.org/cordova/CuttingReleases
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> > >> > > > > > jheifetz@blackberry.com>wrote:
> > >> > > > > > >
> > >> > > > > > >> I can take the responsibility of tagging BlackBerry.
> Could
> > >> you
> > >> > > send
> > >> > > > me
> > >> > > > > > >> the wiki with instructions ?
> > >> > > > > > >>
> > >> > > > > > >> From: Andrew Grieve <agrieve@chromium.org<mailto:
> > >> > > > agrieve@chromium.org
> > >> > > > > >>
> > >> > > > > > >> Date: Thursday, 19 September, 2013 10:40 AM
> > >> > > > > > >> To: dev <dev@cordova.apache.org<mailto:
> > >> dev@cordova.apache.org
> > >> > >>,
> > >> > > > > > Jeffrey
> > >> > > > > > >> Heifetz <jheifetz@blackberry.com<mailto:
> > >> jheifetz@blackberry.com
> > >> > >>
> > >> > > > > > >> Subject: Re: 3.1 Release
> > >> > > > > > >>
> > >> > > > > > >> +Jeffrey - maybe you could take on the BlackBerry
> component
> > >> for
> > >> > > this
> > >> > > > > > >> release?
> > >> > > > > > >>
> > >> > > > > > >>
> > >> > > > > > >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
> > >> > > > > > >> michael@michaelbrooks.ca<mailto:michael@michaelbrooks.ca
> >>
> > >> > wrote:
> > >> > > > > > >> Once the platforms are tagged, I can handle the docs.
> I'll
> > >> need
> > >> > to
> > >> > > > > > review
> > >> > > > > > >> our release process and see how the docs can best abide
> by
> > >> them.
> > >> > > > > > >>
> > >> > > > > > >>
> > >> > > > > > >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <
> > >> > > > agrieve@chromium.org
> > >> > > > > > >> <ma...@chromium.org>> wrote:
> > >> > > > > > >>
> > >> > > > > > >> > Shaz - Thanks for the update :). If iOS is the last one
> > >> then
> > >> > I'd
> > >> > > > say
> > >> > > > > >
> > >>
> > >
> > >
> >
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Sounds good. I don't think we need a release branch on docs if it's not
adding benefit.
On Fri, Sep 20, 2013 at 4:25 AM, Michael Brooks <mi...@michaelbrooks.ca>wrote:
> >
> > Michael: I noticed that the launch bug I created is missing any subtasks
> > for cordova-docs (whoops!). Also - in the current CuttingReleases page,
> we
> > don't actually say that the docs branch should be created until once
> we're
> > ready to launch final. I think this is wrong, but wanted to know what
> your
> > thoughts are for it. I'm thinking:
> > - cordova-docs should have a release branch created as soon as the RCs of
> > the platforms are tagged
> > - I don't think there's much value in having an RC tag for the docs,
> since
> > they tend to change a bunch post RC1 of platforms
> > - cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be
> > made the default. We can keep re-uploading it as changes are made.
> > - Once we're ready for the final release, we delete the rc1 version,
> > upload the non-rc version, and make that the default.
> > Does this sound good?
>
>
> If possible, it would be nice to avoid creating any branches for the
> cordova-docs. When we have a branch, the maintainers need to apply their
> commits to both the master and the release branch. It's error prone and
> troublesome. Since we version cordova-docs by directory, can we skip the
> release branch without messing up the release process? Of course, this is
> temproary. When we switch the a new doc generator and restructure the docs,
> we will version by tags and then we can adopt the release branch approach.
>
> The rest of your steps are exactly how I see it working out.
>
>
> On Thu, Sep 19, 2013 at 8:27 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Sounds good.
> >
> > So - here's what I'm thinking for next steps:
> >
> > Friday:
> > - Remove "core" from plugin IDs
> > - Remove URLs from <dependency> tags
> > - Do a plugins release
> > - Do a plugman release
> > - Do a CLI release, but don't tag it as "latest", tag it as "rc" instead.
> > This will cause it to be installed only if you type "npm install
> cordova@rc
> > "
> > - Add "cordova platform update" instructions to the upgrade guides within
> > the docs
> > - Upload RC1 of cordova-docs
> > - Write blog post about the availability of the RC1. Tweet it.
> >
> > Next Thursday:
> > - If everything seems fine with RC1, release 3.1.0 final.
> >
> > Sound good?
> >
> >
> > Michael: I noticed that the launch bug I created is missing any subtasks
> > for cordova-docs (whoops!). Also - in the current CuttingReleases page,
> we
> > don't actually say that the docs branch should be created until once
> we're
> > ready to launch final. I think this is wrong, but wanted to know what
> your
> > thoughts are for it. I'm thinking:
> > - cordova-docs should have a release branch created as soon as the RCs of
> > the platforms are tagged
> > - I don't think there's much value in having an RC tag for the docs,
> since
> > they tend to change a bunch post RC1 of platforms
> > - cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be
> > made the default. We can keep re-uploading it as changes are made.
> > - Once we're ready for the final release, we delete the rc1 version,
> > upload the non-rc version, and make that the default.
> >
> > Does this sound good?
> >
> >
> >
> > On Thu, Sep 19, 2013 at 11:04 PM, Shazron <sh...@gmail.com> wrote:
> >
> >> Lets skip it, it's unchanged
> >>
> >> On Thursday, September 19, 2013, Andrew Grieve wrote:
> >>
> >> > Thanks Shaz. Do you want to do OSX as well, or should we skip that for
> >> this
> >> > release?
> >> >
> >> >
> >> > On Thu, Sep 19, 2013 at 8:56 PM, Shazron <sh...@gmail.com> wrote:
> >> >
> >> > > ios-deploy stuff a no go so I left it out (check out the issue for
> the
> >> > > sordid details) :(
> >> > >
> >> > > sorry for the delay, I had other pressing work related stuff.
> >> > > Tested mob-spec on iOS 7 and iOS 6 - it works fine, iOS tagged. Only
> >> one
> >> > > failure on iOS 6 - contacts.spec.24.
> >> > >
> >> > >
> >> > > On Thu, Sep 19, 2013 at 10:37 AM, Lorin Beer <
> >> lorin.beer.dev@gmail.com
> >> > > >wrote:
> >> > >
> >> > > > I was away a good chunk of yesterday due to a sick wife, getting
> BB
> >> > > tagged
> >> > > > today. Sorry for the delay.
> >> > > >
> >> > > >
> >> > > > On Thu, Sep 19, 2013 at 9:59 AM, Shazron <sh...@gmail.com>
> wrote:
> >> > > >
> >> > > > > Sorry for the iOS release guys I'm getting it out today
> >> > > > >
> >> > > > >
> >> > > > > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <
> >> mmocny@chromium.org>
> >> > > > wrote:
> >> > > > >
> >> > > > > > Specifically, I think the section "Branch & Tag RC1 for
> Platform
> >> > > > > > Repositories"
> >> > > > > >
> >> > > > > >
> >> > > > > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <
> >> mmocny@chromium.org
> >> > >
> >> > > > > wrote:
> >> > > > > >
> >> > > > > > > I think its this one:
> >> > > http://wiki.apache.org/cordova/CuttingReleases
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> >> > > > > > jheifetz@blackberry.com>wrote:
> >> > > > > > >
> >> > > > > > >> I can take the responsibility of tagging BlackBerry. Could
> >> you
> >> > > send
> >> > > > me
> >> > > > > > >> the wiki with instructions ?
> >> > > > > > >>
> >> > > > > > >> From: Andrew Grieve <agrieve@chromium.org<mailto:
> >> > > > agrieve@chromium.org
> >> > > > > >>
> >> > > > > > >> Date: Thursday, 19 September, 2013 10:40 AM
> >> > > > > > >> To: dev <dev@cordova.apache.org<mailto:
> >> dev@cordova.apache.org
> >> > >>,
> >> > > > > > Jeffrey
> >> > > > > > >> Heifetz <jheifetz@blackberry.com<mailto:
> >> jheifetz@blackberry.com
> >> > >>
> >> > > > > > >> Subject: Re: 3.1 Release
> >> > > > > > >>
> >> > > > > > >> +Jeffrey - maybe you could take on the BlackBerry component
> >> for
> >> > > this
> >> > > > > > >> release?
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > > >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
> >> > > > > > >> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>>
> >> > wrote:
> >> > > > > > >> Once the platforms are tagged, I can handle the docs. I'll
> >> need
> >> > to
> >> > > > > > review
> >> > > > > > >> our release process and see how the docs can best abide by
> >> them.
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > > >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <
> >> > > > agrieve@chromium.org
> >> > > > > > >> <ma...@chromium.org>> wrote:
> >> > > > > > >>
> >> > > > > > >> > Shaz - Thanks for the update :). If iOS is the last one
> >> then
> >> > I'd
> >> > > > say
> >> > > > > >
> >>
> >
> >
>
Re: 3.1 Release
Posted by Michael Brooks <mi...@michaelbrooks.ca>.
>
> Michael: I noticed that the launch bug I created is missing any subtasks
> for cordova-docs (whoops!). Also - in the current CuttingReleases page, we
> don't actually say that the docs branch should be created until once we're
> ready to launch final. I think this is wrong, but wanted to know what your
> thoughts are for it. I'm thinking:
> - cordova-docs should have a release branch created as soon as the RCs of
> the platforms are tagged
> - I don't think there's much value in having an RC tag for the docs, since
> they tend to change a bunch post RC1 of platforms
> - cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be
> made the default. We can keep re-uploading it as changes are made.
> - Once we're ready for the final release, we delete the rc1 version,
> upload the non-rc version, and make that the default.
> Does this sound good?
If possible, it would be nice to avoid creating any branches for the
cordova-docs. When we have a branch, the maintainers need to apply their
commits to both the master and the release branch. It's error prone and
troublesome. Since we version cordova-docs by directory, can we skip the
release branch without messing up the release process? Of course, this is
temproary. When we switch the a new doc generator and restructure the docs,
we will version by tags and then we can adopt the release branch approach.
The rest of your steps are exactly how I see it working out.
On Thu, Sep 19, 2013 at 8:27 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Sounds good.
>
> So - here's what I'm thinking for next steps:
>
> Friday:
> - Remove "core" from plugin IDs
> - Remove URLs from <dependency> tags
> - Do a plugins release
> - Do a plugman release
> - Do a CLI release, but don't tag it as "latest", tag it as "rc" instead.
> This will cause it to be installed only if you type "npm install cordova@rc
> "
> - Add "cordova platform update" instructions to the upgrade guides within
> the docs
> - Upload RC1 of cordova-docs
> - Write blog post about the availability of the RC1. Tweet it.
>
> Next Thursday:
> - If everything seems fine with RC1, release 3.1.0 final.
>
> Sound good?
>
>
> Michael: I noticed that the launch bug I created is missing any subtasks
> for cordova-docs (whoops!). Also - in the current CuttingReleases page, we
> don't actually say that the docs branch should be created until once we're
> ready to launch final. I think this is wrong, but wanted to know what your
> thoughts are for it. I'm thinking:
> - cordova-docs should have a release branch created as soon as the RCs of
> the platforms are tagged
> - I don't think there's much value in having an RC tag for the docs, since
> they tend to change a bunch post RC1 of platforms
> - cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be
> made the default. We can keep re-uploading it as changes are made.
> - Once we're ready for the final release, we delete the rc1 version,
> upload the non-rc version, and make that the default.
>
> Does this sound good?
>
>
>
> On Thu, Sep 19, 2013 at 11:04 PM, Shazron <sh...@gmail.com> wrote:
>
>> Lets skip it, it's unchanged
>>
>> On Thursday, September 19, 2013, Andrew Grieve wrote:
>>
>> > Thanks Shaz. Do you want to do OSX as well, or should we skip that for
>> this
>> > release?
>> >
>> >
>> > On Thu, Sep 19, 2013 at 8:56 PM, Shazron <sh...@gmail.com> wrote:
>> >
>> > > ios-deploy stuff a no go so I left it out (check out the issue for the
>> > > sordid details) :(
>> > >
>> > > sorry for the delay, I had other pressing work related stuff.
>> > > Tested mob-spec on iOS 7 and iOS 6 - it works fine, iOS tagged. Only
>> one
>> > > failure on iOS 6 - contacts.spec.24.
>> > >
>> > >
>> > > On Thu, Sep 19, 2013 at 10:37 AM, Lorin Beer <
>> lorin.beer.dev@gmail.com
>> > > >wrote:
>> > >
>> > > > I was away a good chunk of yesterday due to a sick wife, getting BB
>> > > tagged
>> > > > today. Sorry for the delay.
>> > > >
>> > > >
>> > > > On Thu, Sep 19, 2013 at 9:59 AM, Shazron <sh...@gmail.com> wrote:
>> > > >
>> > > > > Sorry for the iOS release guys I'm getting it out today
>> > > > >
>> > > > >
>> > > > > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <
>> mmocny@chromium.org>
>> > > > wrote:
>> > > > >
>> > > > > > Specifically, I think the section "Branch & Tag RC1 for Platform
>> > > > > > Repositories"
>> > > > > >
>> > > > > >
>> > > > > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <
>> mmocny@chromium.org
>> > >
>> > > > > wrote:
>> > > > > >
>> > > > > > > I think its this one:
>> > > http://wiki.apache.org/cordova/CuttingReleases
>> > > > > > >
>> > > > > > >
>> > > > > > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
>> > > > > > jheifetz@blackberry.com>wrote:
>> > > > > > >
>> > > > > > >> I can take the responsibility of tagging BlackBerry. Could
>> you
>> > > send
>> > > > me
>> > > > > > >> the wiki with instructions ?
>> > > > > > >>
>> > > > > > >> From: Andrew Grieve <agrieve@chromium.org<mailto:
>> > > > agrieve@chromium.org
>> > > > > >>
>> > > > > > >> Date: Thursday, 19 September, 2013 10:40 AM
>> > > > > > >> To: dev <dev@cordova.apache.org<mailto:
>> dev@cordova.apache.org
>> > >>,
>> > > > > > Jeffrey
>> > > > > > >> Heifetz <jheifetz@blackberry.com<mailto:
>> jheifetz@blackberry.com
>> > >>
>> > > > > > >> Subject: Re: 3.1 Release
>> > > > > > >>
>> > > > > > >> +Jeffrey - maybe you could take on the BlackBerry component
>> for
>> > > this
>> > > > > > >> release?
>> > > > > > >>
>> > > > > > >>
>> > > > > > >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
>> > > > > > >> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>>
>> > wrote:
>> > > > > > >> Once the platforms are tagged, I can handle the docs. I'll
>> need
>> > to
>> > > > > > review
>> > > > > > >> our release process and see how the docs can best abide by
>> them.
>> > > > > > >>
>> > > > > > >>
>> > > > > > >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <
>> > > > agrieve@chromium.org
>> > > > > > >> <ma...@chromium.org>> wrote:
>> > > > > > >>
>> > > > > > >> > Shaz - Thanks for the update :). If iOS is the last one
>> then
>> > I'd
>> > > > say
>> > > > > >
>>
>
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Sounds good.
So - here's what I'm thinking for next steps:
Friday:
- Remove "core" from plugin IDs
- Remove URLs from <dependency> tags
- Do a plugins release
- Do a plugman release
- Do a CLI release, but don't tag it as "latest", tag it as "rc" instead.
This will cause it to be installed only if you type "npm install cordova@rc"
- Add "cordova platform update" instructions to the upgrade guides within
the docs
- Upload RC1 of cordova-docs
- Write blog post about the availability of the RC1. Tweet it.
Next Thursday:
- If everything seems fine with RC1, release 3.1.0 final.
Sound good?
Michael: I noticed that the launch bug I created is missing any subtasks
for cordova-docs (whoops!). Also - in the current CuttingReleases page, we
don't actually say that the docs branch should be created until once we're
ready to launch final. I think this is wrong, but wanted to know what your
thoughts are for it. I'm thinking:
- cordova-docs should have a release branch created as soon as the RCs of
the platforms are tagged
- I don't think there's much value in having an RC tag for the docs, since
they tend to change a bunch post RC1 of platforms
- cordova-docs 3.1.0-rc1 should be uploaded to the website, but not be made
the default. We can keep re-uploading it as changes are made.
- Once we're ready for the final release, we delete the rc1 version, upload
the non-rc version, and make that the default.
Does this sound good?
On Thu, Sep 19, 2013 at 11:04 PM, Shazron <sh...@gmail.com> wrote:
> Lets skip it, it's unchanged
>
> On Thursday, September 19, 2013, Andrew Grieve wrote:
>
> > Thanks Shaz. Do you want to do OSX as well, or should we skip that for
> this
> > release?
> >
> >
> > On Thu, Sep 19, 2013 at 8:56 PM, Shazron <sh...@gmail.com> wrote:
> >
> > > ios-deploy stuff a no go so I left it out (check out the issue for the
> > > sordid details) :(
> > >
> > > sorry for the delay, I had other pressing work related stuff.
> > > Tested mob-spec on iOS 7 and iOS 6 - it works fine, iOS tagged. Only
> one
> > > failure on iOS 6 - contacts.spec.24.
> > >
> > >
> > > On Thu, Sep 19, 2013 at 10:37 AM, Lorin Beer <lorin.beer.dev@gmail.com
> > > >wrote:
> > >
> > > > I was away a good chunk of yesterday due to a sick wife, getting BB
> > > tagged
> > > > today. Sorry for the delay.
> > > >
> > > >
> > > > On Thu, Sep 19, 2013 at 9:59 AM, Shazron <sh...@gmail.com> wrote:
> > > >
> > > > > Sorry for the iOS release guys I'm getting it out today
> > > > >
> > > > >
> > > > > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <mmocny@chromium.org
> >
> > > > wrote:
> > > > >
> > > > > > Specifically, I think the section "Branch & Tag RC1 for Platform
> > > > > > Repositories"
> > > > > >
> > > > > >
> > > > > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <
> mmocny@chromium.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > I think its this one:
> > > http://wiki.apache.org/cordova/CuttingReleases
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> > > > > > jheifetz@blackberry.com>wrote:
> > > > > > >
> > > > > > >> I can take the responsibility of tagging BlackBerry. Could you
> > > send
> > > > me
> > > > > > >> the wiki with instructions ?
> > > > > > >>
> > > > > > >> From: Andrew Grieve <agrieve@chromium.org<mailto:
> > > > agrieve@chromium.org
> > > > > >>
> > > > > > >> Date: Thursday, 19 September, 2013 10:40 AM
> > > > > > >> To: dev <dev@cordova.apache.org<mailto:dev@cordova.apache.org
> > >>,
> > > > > > Jeffrey
> > > > > > >> Heifetz <jheifetz@blackberry.com<mailto:
> jheifetz@blackberry.com
> > >>
> > > > > > >> Subject: Re: 3.1 Release
> > > > > > >>
> > > > > > >> +Jeffrey - maybe you could take on the BlackBerry component
> for
> > > this
> > > > > > >> release?
> > > > > > >>
> > > > > > >>
> > > > > > >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
> > > > > > >> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>>
> > wrote:
> > > > > > >> Once the platforms are tagged, I can handle the docs. I'll
> need
> > to
> > > > > > review
> > > > > > >> our release process and see how the docs can best abide by
> them.
> > > > > > >>
> > > > > > >>
> > > > > > >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <
> > > > agrieve@chromium.org
> > > > > > >> <ma...@chromium.org>> wrote:
> > > > > > >>
> > > > > > >> > Shaz - Thanks for the update :). If iOS is the last one then
> > I'd
> > > > say
> > > > > >
>
Re: 3.1 Release
Posted by Shazron <sh...@gmail.com>.
Lets skip it, it's unchanged
On Thursday, September 19, 2013, Andrew Grieve wrote:
> Thanks Shaz. Do you want to do OSX as well, or should we skip that for this
> release?
>
>
> On Thu, Sep 19, 2013 at 8:56 PM, Shazron <sh...@gmail.com> wrote:
>
> > ios-deploy stuff a no go so I left it out (check out the issue for the
> > sordid details) :(
> >
> > sorry for the delay, I had other pressing work related stuff.
> > Tested mob-spec on iOS 7 and iOS 6 - it works fine, iOS tagged. Only one
> > failure on iOS 6 - contacts.spec.24.
> >
> >
> > On Thu, Sep 19, 2013 at 10:37 AM, Lorin Beer <lorin.beer.dev@gmail.com
> > >wrote:
> >
> > > I was away a good chunk of yesterday due to a sick wife, getting BB
> > tagged
> > > today. Sorry for the delay.
> > >
> > >
> > > On Thu, Sep 19, 2013 at 9:59 AM, Shazron <sh...@gmail.com> wrote:
> > >
> > > > Sorry for the iOS release guys I'm getting it out today
> > > >
> > > >
> > > > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <mm...@chromium.org>
> > > wrote:
> > > >
> > > > > Specifically, I think the section "Branch & Tag RC1 for Platform
> > > > > Repositories"
> > > > >
> > > > >
> > > > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <mmocny@chromium.org
> >
> > > > wrote:
> > > > >
> > > > > > I think its this one:
> > http://wiki.apache.org/cordova/CuttingReleases
> > > > > >
> > > > > >
> > > > > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> > > > > jheifetz@blackberry.com>wrote:
> > > > > >
> > > > > >> I can take the responsibility of tagging BlackBerry. Could you
> > send
> > > me
> > > > > >> the wiki with instructions ?
> > > > > >>
> > > > > >> From: Andrew Grieve <agrieve@chromium.org<mailto:
> > > agrieve@chromium.org
> > > > >>
> > > > > >> Date: Thursday, 19 September, 2013 10:40 AM
> > > > > >> To: dev <dev@cordova.apache.org<mailto:dev@cordova.apache.org
> >>,
> > > > > Jeffrey
> > > > > >> Heifetz <jheifetz@blackberry.com<mailto:jheifetz@blackberry.com
> >>
> > > > > >> Subject: Re: 3.1 Release
> > > > > >>
> > > > > >> +Jeffrey - maybe you could take on the BlackBerry component for
> > this
> > > > > >> release?
> > > > > >>
> > > > > >>
> > > > > >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
> > > > > >> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>>
> wrote:
> > > > > >> Once the platforms are tagged, I can handle the docs. I'll need
> to
> > > > > review
> > > > > >> our release process and see how the docs can best abide by them.
> > > > > >>
> > > > > >>
> > > > > >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <
> > > agrieve@chromium.org
> > > > > >> <ma...@chromium.org>> wrote:
> > > > > >>
> > > > > >> > Shaz - Thanks for the update :). If iOS is the last one then
> I'd
> > > say
> > > > >
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Thanks Shaz. Do you want to do OSX as well, or should we skip that for this
release?
On Thu, Sep 19, 2013 at 8:56 PM, Shazron <sh...@gmail.com> wrote:
> ios-deploy stuff a no go so I left it out (check out the issue for the
> sordid details) :(
>
> sorry for the delay, I had other pressing work related stuff.
> Tested mob-spec on iOS 7 and iOS 6 - it works fine, iOS tagged. Only one
> failure on iOS 6 - contacts.spec.24.
>
>
> On Thu, Sep 19, 2013 at 10:37 AM, Lorin Beer <lorin.beer.dev@gmail.com
> >wrote:
>
> > I was away a good chunk of yesterday due to a sick wife, getting BB
> tagged
> > today. Sorry for the delay.
> >
> >
> > On Thu, Sep 19, 2013 at 9:59 AM, Shazron <sh...@gmail.com> wrote:
> >
> > > Sorry for the iOS release guys I'm getting it out today
> > >
> > >
> > > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >
> > > > Specifically, I think the section "Branch & Tag RC1 for Platform
> > > > Repositories"
> > > >
> > > >
> > > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <mm...@chromium.org>
> > > wrote:
> > > >
> > > > > I think its this one:
> http://wiki.apache.org/cordova/CuttingReleases
> > > > >
> > > > >
> > > > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> > > > jheifetz@blackberry.com>wrote:
> > > > >
> > > > >> I can take the responsibility of tagging BlackBerry. Could you
> send
> > me
> > > > >> the wiki with instructions ?
> > > > >>
> > > > >> From: Andrew Grieve <agrieve@chromium.org<mailto:
> > agrieve@chromium.org
> > > >>
> > > > >> Date: Thursday, 19 September, 2013 10:40 AM
> > > > >> To: dev <de...@cordova.apache.org>>,
> > > > Jeffrey
> > > > >> Heifetz <jh...@blackberry.com>>
> > > > >> Subject: Re: 3.1 Release
> > > > >>
> > > > >> +Jeffrey - maybe you could take on the BlackBerry component for
> this
> > > > >> release?
> > > > >>
> > > > >>
> > > > >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
> > > > >> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>> wrote:
> > > > >> Once the platforms are tagged, I can handle the docs. I'll need to
> > > > review
> > > > >> our release process and see how the docs can best abide by them.
> > > > >>
> > > > >>
> > > > >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <
> > agrieve@chromium.org
> > > > >> <ma...@chromium.org>> wrote:
> > > > >>
> > > > >> > Shaz - Thanks for the update :). If iOS is the last one then I'd
> > say
> > > > >> let's
> > > > >> > go without, but maybe keep at it until we get BB tagged? (just
> my
> > > > >> opinion)
> > > > >> >
> > > > >> > Heading home now - anyone know if Lorin is away or not?
> > > > >> >
> > > > >> >
> > > > >> > On Wed, Sep 18, 2013 at 3:35 PM, Shazron <shazron@gmail.com
> > <mailto:
> > > > >> shazron@gmail.com>> wrote:
> > > > >> >
> > > > >> > > When i mean ios-deploy still works, it _installs_ it on the
> > > device,
> > > > >> but
> > > > >> > > does _not_ run it.
> > > > >> > >
> > > > >> > >
> > > > >> > > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <shazron@gmail.com
> > > > <mailto:
> > > > >> shazron@gmail.com>> wrote:
> > > > >> > >
> > > > >> > >> I'm 99% done with iOS specific fixes. One last one I'm trying
> > to
> > > do
> > > > >> is
> > > > >> > >> ios-deploy with lldb:
> > > > https://issues.apache.org/jira/browse/CB-4804
> > > > >> > >>
> > > > >> > >> This means if I don't get this fix in, we _can_ deploy from
> the
> > > > >> command
> > > > >> > >> line using ios-deploy _but_ we can't attach to the debugger.
> > Will
> > > > >> that
> > > > >> > be
> > > > >> > >> acceptable you think?
> > > > >> > >>
> > > > >> > >>
> > > > >> > >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <
> > > > >> agrieve@chromium.org<ma...@chromium.org>
> > > > >> > >wrote:
> > > > >> > >>
> > > > >> > >>> Ping Lorin & Shaz.
> > > > >> > >>>
> > > > >> > >>>
> > > > >> > >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <
> > > > >> stevengill97@gmail.com<ma...@gmail.com>
> > > > >> > >wrote:
> > > > >> > >>>
> > > > >> > >>>> FFOS will be tagged tomorrow. I have a few changes I am
> going
> > > to
> > > > >> get
> > > > >> > in
> > > > >> > >>>> tomorrow before tagging but it will be good to go very
> soon!
> > > > >> > >>>>
> > > > >> > >>>> With FFOS, Only two plugins have been ported so far
> > (vibration
> > > > and
> > > > >> > >>>> device).
> > > > >> > >>>> We are going to continue to add firefoxos support to
> plugins
> > > post
> > > > >> > >>>> release.
> > > > >> > >>>> I don't think we should start officially promoting support
> > for
> > > > FFOS
> > > > >> > >>>> until
> > > > >> > >>>> we have more plugins. For 3.1, it will be available for
> users
> > > to
> > > > >> try
> > > > >> > >>>> out,
> > > > >> > >>>> test, give feedback, etc.
> > > > >> > >>>>
> > > > >> > >>>> Cheers,
> > > > >> > >>>> -Steve
> > > > >> > >>>>
> > > > >> > >>>>
> > > > >> > >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <
> > > > >> agrieve@chromium.org<ma...@chromium.org>>
> > > > >> > >>>> wrote:
> > > > >> > >>>>
> > > > >> > >>>> > Thanks Jesse! Great work on being on top of things. If
> > > changes
> > > > >> were
> > > > >> > >>>> done in
> > > > >> > >>>> > plugin repos, then those aren't a part of this release
> > > anyways
> > > > >> and
> > > > >> > >>>> will be
> > > > >> > >>>> > picked up by the RELEASENOTES.md within the plugin repos
> on
> > > the
> > > > >> next
> > > > >> > >>>> > plugins release.
> > > > >> > >>>> >
> > > > >> > >>>> > I think it's up to you if you want to start writing
> > > > >> RELEASENOTES.md
> > > > >> > >>>> for
> > > > >> > >>>> > WP7+8. My thinking was just that doing so would make
> > release
> > > > >> > >>>> announcements
> > > > >> > >>>> > easier.
> > > > >> > >>>> >
> > > > >> > >>>> > Since WP7 and WP8 are in the same repo, does it make
> sense
> > to
> > > > >> have
> > > > >> > >>>> > different subtasks for their taggings? If so, I'll add it
> > to
> > > > the
> > > > >> > >>>> template,
> > > > >> > >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> > > > >> > >>>> >
> > > > >> > >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you
> > > think
> > > > >> > you'll
> > > > >> > >>>> be
> > > > >> > >>>> > able to tag iOS / OSX soon?
> > > > >> > >>>> > Lorin - Same question for BB. Will you be able to write
> an
> > > > update
> > > > >> > >>>> script
> > > > >> > >>>> > for it (CB-4776)
> > > > >> > >>>> > Steve - Likewise for FF
> > > > >> > >>>> >
> > > > >> > >>>> > I'd really like this tagging to be done tomorrow so that
> we
> > > can
> > > > >> test
> > > > >> > >>>> out
> > > > >> > >>>> > RC1 using RC1 of CLI.
> > > > >> > >>>> >
> > > > >> > >>>> >
> > > > >> > >>>> >
> > > > >> > >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <
> > > > purplecabbage@gmail.com
> > > > >> <ma...@gmail.com>>
> > > > >> > >>>> wrote:
> > > > >> > >>>> >
> > > > >> > >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> > > > >> > >>>> > >
> > > > >> > >>>> > > re: Changelog
> > > > >> > >>>> > > It is a little more difficult in these cases, and I
> n'er
> > > > >> > >>>> volunteered to
> > > > >> > >>>> > do
> > > > >> > >>>> > > it, so whatevs
> > > > >> > >>>> > > - WP7+8 live in one repo, so their changes would need
> to
> > be
> > > > >> > demuxed
> > > > >> > >>>> > > - all the changes for Windows8 have happened in the
> > plugin
> > > > >> repos,
> > > > >> > >>>> and
> > > > >> > >>>> > > cordova-js, so changelog would be empty
> > > > >> > >>>> > >
> > > > >> > >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
> > > > >> > >>>> > >
> > > > >> > >>>> > >
> > > > >> > >>>> > >
> > > > >> > >>>> > >
> > > > >> > >>>> > > @purplecabbage
> > > > >> > >>>> > > risingj.com<http://risingj.com>
> > > > >> > >>>> > >
> > > > >> > >>>> > >
> > > > >> > >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
> > > > >> > >>>> agrieve@chromium.org<ma...@chromium.org>
> > > > >> > >>>> > > >wrote:
> > > > >> > >>>> > >
> > > > >> > >>>> > > > For the last plugin release, I tagged them with the
> > > > plugin's
> > > > >> > >>>> version.
> > > > >> > >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins
> > that
> > > > had
> > > > >> > >>>> changes
> > > > >> > >>>> > were
> > > > >> > >>>> > > > included in the release, so some may still not have
> any
> > > > >> release
> > > > >> > >>>> tags.
> > > > >> > >>>> > > >
> > > > >> > >>>> > > >
> > > > >> > >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> > > > >> > >>>> > braden@chromium.org<ma...@chromium.org>
> > > > >> > >>>> > > > >wrote:
> > > > >> > >>>> > > >
> > > > >> > >>>> > > > > My understanding is that the plugins are totally
> > > > >> independent
> > > > >> > of
> > > > >> > >>>> > Cordova
> > > > >> > >>>> > > > > versions, and release on their own
> > > > >> weekly-at-the-most-frequent
> > > > >> > >>>> cycle.
> > > > >> > >>>> > > > >
> > > > >> > >>>> > > > > They only depend on Cordova versions when they
> need a
> > > > >> > >>>> sufficiently
> > > > >> > >>>> > new
> > > > >> > >>>> > > > > platform to support some feature (binary bridge,
> for
> > > > >> example),
> > > > >> > >>>> and
> > > > >> > >>>> > then
> > > > >> > >>>> > > > > they set <engine> tags appropriately.
> > > > >> > >>>> > > > >
> > > > >> > >>>> > > > > Braden
> > > > >> > >>>> > > > >
> > > > >> > >>>> > > > >
> > > > >> > >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
> > > > >> > >>>> cmarcelk@gmail.com<ma...@gmail.com>>
> > > > >> > >>>> > > > wrote:
> > > > >> > >>>> > > > >
> > > > >> > >>>> > > > > > Will the plugin repos get tagged? If so, do they
> > get
> > > > >> tagged
> > > > >> > on
> > > > >> > >>>> > every
> > > > >> > >>>> > > > > > weekly cycle, or only when a cadence lines up
> with
> > a
> > > > >> weekly
> > > > >> > >>>> cycle,
> > > > >> > >>>> > or
> > > > >> > >>>> > > > > both?
> > > > >> > >>>> > > > > >
> > > > >> > >>>> > > > > > I see that StepsForPluginRelease wiki say it will
> > > > happen,
> > > > >> > and
> > > > >> > >>>> the
> > > > >> > >>>> > > most
> > > > >> > >>>> > > > > > recent coho looks like it will do it, but I
> > currently
> > > > see
> > > > >> > >>>> only tags
> > > > >> > >>>> > > for
> > > > >> > >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a
> > > "weekly"
> > > > >> tag.
> > > > >> > >>>> > Thanks!
> > > > >> > >>>> > > > > >
> > > > >> > >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> > > > >> > >>>> agrieve@chromium.org<ma...@chromium.org>>
> > > > >> > >>>> > > > wrote:
> > > > >> > >>>> > > > > >
> > > > >> > >>>> > > > > > > I think it's time to get the ball rolling on
> > this.
> > > > >> It'll
> > > > >> > be
> > > > >> > >>>> the
> > > > >> > >>>> > > first
> > > > >> > >>>> > > > > > > release post-3.0, so will likely have a few
> bumps
> > > to
> > > > >> work
> > > > >> > >>>> > through.
> > > > >> > >>>> > > > > > >
> > > > >> > >>>> > > > > > > How about:
> > > > >> > >>>> > > > > > >
> > > > >> > >>>> > > > > > > Friday 13th - Create release branches & tag RC
> of
> > > all
> > > > >> > repos
> > > > >> > >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest
> of
> > > > >> > changelogs)
> > > > >> > >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> > > > >> > >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm &
> Post
> > > blog
> > > > >> post
> > > > >> > >>>> > > > > > >
> > > > >> > >>>> > > > > > > The main feature of this release will be
> > > > >> plugman-registry
> > > > >> > I
> > > > >> > >>>> > think.
> > > > >> > >>>> > > > That
> > > > >> > >>>> > > > > > > said, since CLI / Plugman aren't tied to
> cadence
> > > > >> > releases, I
> > > > >> > >>>> > think
> > > > >> > >>>> > > > it's
> > > > >> > >>>> > > > > > > just cordova-docs that is relevant.
> > > > >> > >>>> > > > > >
> > > > >> > >>>> > > > > >
> > > > >> > >>>> > > > >
> > > > >> > >>>> > > >
> > > > >> > >>>> > >
> > > > >> > >>>> >
> > > > >> > >>>>
> > > > >> > >>>
> > > > >> > >>>
> > > > >> > >>
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> This transmission (including any attachments) may contain
> > confidential
> > > > >> information, privileged material (including material protected by
> > the
> > > > >> solicitor-client or other applicable privileges), or constitute
> > > > non-public
> > > > >> information. Any use of this information by anyone other than the
> > > > intended
> > > > >> recipient is prohibited. If you have received this transmission in
> > > > error,
> > > > >> please immediately reply to the sender and delete this information
> > > from
> > > > >> your system. Use, dissemination, distribution, or reproduction of
> > this
> > > > >> transmission by unintended recipients is not authorized and may be
> > > > unlawful.
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>
Re: 3.1 Release
Posted by Shazron <sh...@gmail.com>.
ios-deploy stuff a no go so I left it out (check out the issue for the
sordid details) :(
sorry for the delay, I had other pressing work related stuff.
Tested mob-spec on iOS 7 and iOS 6 - it works fine, iOS tagged. Only one
failure on iOS 6 - contacts.spec.24.
On Thu, Sep 19, 2013 at 10:37 AM, Lorin Beer <lo...@gmail.com>wrote:
> I was away a good chunk of yesterday due to a sick wife, getting BB tagged
> today. Sorry for the delay.
>
>
> On Thu, Sep 19, 2013 at 9:59 AM, Shazron <sh...@gmail.com> wrote:
>
> > Sorry for the iOS release guys I'm getting it out today
> >
> >
> > On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > Specifically, I think the section "Branch & Tag RC1 for Platform
> > > Repositories"
> > >
> > >
> > > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <mm...@chromium.org>
> > wrote:
> > >
> > > > I think its this one: http://wiki.apache.org/cordova/CuttingReleases
> > > >
> > > >
> > > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> > > jheifetz@blackberry.com>wrote:
> > > >
> > > >> I can take the responsibility of tagging BlackBerry. Could you send
> me
> > > >> the wiki with instructions ?
> > > >>
> > > >> From: Andrew Grieve <agrieve@chromium.org<mailto:
> agrieve@chromium.org
> > >>
> > > >> Date: Thursday, 19 September, 2013 10:40 AM
> > > >> To: dev <de...@cordova.apache.org>>,
> > > Jeffrey
> > > >> Heifetz <jh...@blackberry.com>>
> > > >> Subject: Re: 3.1 Release
> > > >>
> > > >> +Jeffrey - maybe you could take on the BlackBerry component for this
> > > >> release?
> > > >>
> > > >>
> > > >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
> > > >> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>> wrote:
> > > >> Once the platforms are tagged, I can handle the docs. I'll need to
> > > review
> > > >> our release process and see how the docs can best abide by them.
> > > >>
> > > >>
> > > >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <
> agrieve@chromium.org
> > > >> <ma...@chromium.org>> wrote:
> > > >>
> > > >> > Shaz - Thanks for the update :). If iOS is the last one then I'd
> say
> > > >> let's
> > > >> > go without, but maybe keep at it until we get BB tagged? (just my
> > > >> opinion)
> > > >> >
> > > >> > Heading home now - anyone know if Lorin is away or not?
> > > >> >
> > > >> >
> > > >> > On Wed, Sep 18, 2013 at 3:35 PM, Shazron <shazron@gmail.com
> <mailto:
> > > >> shazron@gmail.com>> wrote:
> > > >> >
> > > >> > > When i mean ios-deploy still works, it _installs_ it on the
> > device,
> > > >> but
> > > >> > > does _not_ run it.
> > > >> > >
> > > >> > >
> > > >> > > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <shazron@gmail.com
> > > <mailto:
> > > >> shazron@gmail.com>> wrote:
> > > >> > >
> > > >> > >> I'm 99% done with iOS specific fixes. One last one I'm trying
> to
> > do
> > > >> is
> > > >> > >> ios-deploy with lldb:
> > > https://issues.apache.org/jira/browse/CB-4804
> > > >> > >>
> > > >> > >> This means if I don't get this fix in, we _can_ deploy from the
> > > >> command
> > > >> > >> line using ios-deploy _but_ we can't attach to the debugger.
> Will
> > > >> that
> > > >> > be
> > > >> > >> acceptable you think?
> > > >> > >>
> > > >> > >>
> > > >> > >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <
> > > >> agrieve@chromium.org<ma...@chromium.org>
> > > >> > >wrote:
> > > >> > >>
> > > >> > >>> Ping Lorin & Shaz.
> > > >> > >>>
> > > >> > >>>
> > > >> > >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <
> > > >> stevengill97@gmail.com<ma...@gmail.com>
> > > >> > >wrote:
> > > >> > >>>
> > > >> > >>>> FFOS will be tagged tomorrow. I have a few changes I am going
> > to
> > > >> get
> > > >> > in
> > > >> > >>>> tomorrow before tagging but it will be good to go very soon!
> > > >> > >>>>
> > > >> > >>>> With FFOS, Only two plugins have been ported so far
> (vibration
> > > and
> > > >> > >>>> device).
> > > >> > >>>> We are going to continue to add firefoxos support to plugins
> > post
> > > >> > >>>> release.
> > > >> > >>>> I don't think we should start officially promoting support
> for
> > > FFOS
> > > >> > >>>> until
> > > >> > >>>> we have more plugins. For 3.1, it will be available for users
> > to
> > > >> try
> > > >> > >>>> out,
> > > >> > >>>> test, give feedback, etc.
> > > >> > >>>>
> > > >> > >>>> Cheers,
> > > >> > >>>> -Steve
> > > >> > >>>>
> > > >> > >>>>
> > > >> > >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <
> > > >> agrieve@chromium.org<ma...@chromium.org>>
> > > >> > >>>> wrote:
> > > >> > >>>>
> > > >> > >>>> > Thanks Jesse! Great work on being on top of things. If
> > changes
> > > >> were
> > > >> > >>>> done in
> > > >> > >>>> > plugin repos, then those aren't a part of this release
> > anyways
> > > >> and
> > > >> > >>>> will be
> > > >> > >>>> > picked up by the RELEASENOTES.md within the plugin repos on
> > the
> > > >> next
> > > >> > >>>> > plugins release.
> > > >> > >>>> >
> > > >> > >>>> > I think it's up to you if you want to start writing
> > > >> RELEASENOTES.md
> > > >> > >>>> for
> > > >> > >>>> > WP7+8. My thinking was just that doing so would make
> release
> > > >> > >>>> announcements
> > > >> > >>>> > easier.
> > > >> > >>>> >
> > > >> > >>>> > Since WP7 and WP8 are in the same repo, does it make sense
> to
> > > >> have
> > > >> > >>>> > different subtasks for their taggings? If so, I'll add it
> to
> > > the
> > > >> > >>>> template,
> > > >> > >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> > > >> > >>>> >
> > > >> > >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you
> > think
> > > >> > you'll
> > > >> > >>>> be
> > > >> > >>>> > able to tag iOS / OSX soon?
> > > >> > >>>> > Lorin - Same question for BB. Will you be able to write an
> > > update
> > > >> > >>>> script
> > > >> > >>>> > for it (CB-4776)
> > > >> > >>>> > Steve - Likewise for FF
> > > >> > >>>> >
> > > >> > >>>> > I'd really like this tagging to be done tomorrow so that we
> > can
> > > >> test
> > > >> > >>>> out
> > > >> > >>>> > RC1 using RC1 of CLI.
> > > >> > >>>> >
> > > >> > >>>> >
> > > >> > >>>> >
> > > >> > >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <
> > > purplecabbage@gmail.com
> > > >> <ma...@gmail.com>>
> > > >> > >>>> wrote:
> > > >> > >>>> >
> > > >> > >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> > > >> > >>>> > >
> > > >> > >>>> > > re: Changelog
> > > >> > >>>> > > It is a little more difficult in these cases, and I n'er
> > > >> > >>>> volunteered to
> > > >> > >>>> > do
> > > >> > >>>> > > it, so whatevs
> > > >> > >>>> > > - WP7+8 live in one repo, so their changes would need to
> be
> > > >> > demuxed
> > > >> > >>>> > > - all the changes for Windows8 have happened in the
> plugin
> > > >> repos,
> > > >> > >>>> and
> > > >> > >>>> > > cordova-js, so changelog would be empty
> > > >> > >>>> > >
> > > >> > >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
> > > >> > >>>> > >
> > > >> > >>>> > >
> > > >> > >>>> > >
> > > >> > >>>> > >
> > > >> > >>>> > > @purplecabbage
> > > >> > >>>> > > risingj.com<http://risingj.com>
> > > >> > >>>> > >
> > > >> > >>>> > >
> > > >> > >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
> > > >> > >>>> agrieve@chromium.org<ma...@chromium.org>
> > > >> > >>>> > > >wrote:
> > > >> > >>>> > >
> > > >> > >>>> > > > For the last plugin release, I tagged them with the
> > > plugin's
> > > >> > >>>> version.
> > > >> > >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins
> that
> > > had
> > > >> > >>>> changes
> > > >> > >>>> > were
> > > >> > >>>> > > > included in the release, so some may still not have any
> > > >> release
> > > >> > >>>> tags.
> > > >> > >>>> > > >
> > > >> > >>>> > > >
> > > >> > >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> > > >> > >>>> > braden@chromium.org<ma...@chromium.org>
> > > >> > >>>> > > > >wrote:
> > > >> > >>>> > > >
> > > >> > >>>> > > > > My understanding is that the plugins are totally
> > > >> independent
> > > >> > of
> > > >> > >>>> > Cordova
> > > >> > >>>> > > > > versions, and release on their own
> > > >> weekly-at-the-most-frequent
> > > >> > >>>> cycle.
> > > >> > >>>> > > > >
> > > >> > >>>> > > > > They only depend on Cordova versions when they need a
> > > >> > >>>> sufficiently
> > > >> > >>>> > new
> > > >> > >>>> > > > > platform to support some feature (binary bridge, for
> > > >> example),
> > > >> > >>>> and
> > > >> > >>>> > then
> > > >> > >>>> > > > > they set <engine> tags appropriately.
> > > >> > >>>> > > > >
> > > >> > >>>> > > > > Braden
> > > >> > >>>> > > > >
> > > >> > >>>> > > > >
> > > >> > >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
> > > >> > >>>> cmarcelk@gmail.com<ma...@gmail.com>>
> > > >> > >>>> > > > wrote:
> > > >> > >>>> > > > >
> > > >> > >>>> > > > > > Will the plugin repos get tagged? If so, do they
> get
> > > >> tagged
> > > >> > on
> > > >> > >>>> > every
> > > >> > >>>> > > > > > weekly cycle, or only when a cadence lines up with
> a
> > > >> weekly
> > > >> > >>>> cycle,
> > > >> > >>>> > or
> > > >> > >>>> > > > > both?
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > > > I see that StepsForPluginRelease wiki say it will
> > > happen,
> > > >> > and
> > > >> > >>>> the
> > > >> > >>>> > > most
> > > >> > >>>> > > > > > recent coho looks like it will do it, but I
> currently
> > > see
> > > >> > >>>> only tags
> > > >> > >>>> > > for
> > > >> > >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a
> > "weekly"
> > > >> tag.
> > > >> > >>>> > Thanks!
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> > > >> > >>>> agrieve@chromium.org<ma...@chromium.org>>
> > > >> > >>>> > > > wrote:
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > > > > I think it's time to get the ball rolling on
> this.
> > > >> It'll
> > > >> > be
> > > >> > >>>> the
> > > >> > >>>> > > first
> > > >> > >>>> > > > > > > release post-3.0, so will likely have a few bumps
> > to
> > > >> work
> > > >> > >>>> > through.
> > > >> > >>>> > > > > > >
> > > >> > >>>> > > > > > > How about:
> > > >> > >>>> > > > > > >
> > > >> > >>>> > > > > > > Friday 13th - Create release branches & tag RC of
> > all
> > > >> > repos
> > > >> > >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of
> > > >> > changelogs)
> > > >> > >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> > > >> > >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post
> > blog
> > > >> post
> > > >> > >>>> > > > > > >
> > > >> > >>>> > > > > > > The main feature of this release will be
> > > >> plugman-registry
> > > >> > I
> > > >> > >>>> > think.
> > > >> > >>>> > > > That
> > > >> > >>>> > > > > > > said, since CLI / Plugman aren't tied to cadence
> > > >> > releases, I
> > > >> > >>>> > think
> > > >> > >>>> > > > it's
> > > >> > >>>> > > > > > > just cordova-docs that is relevant.
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > > >
> > > >> > >>>> > > > >
> > > >> > >>>> > > >
> > > >> > >>>> > >
> > > >> > >>>> >
> > > >> > >>>>
> > > >> > >>>
> > > >> > >>>
> > > >> > >>
> > > >> > >
> > > >> >
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> This transmission (including any attachments) may contain
> confidential
> > > >> information, privileged material (including material protected by
> the
> > > >> solicitor-client or other applicable privileges), or constitute
> > > non-public
> > > >> information. Any use of this information by anyone other than the
> > > intended
> > > >> recipient is prohibited. If you have received this transmission in
> > > error,
> > > >> please immediately reply to the sender and delete this information
> > from
> > > >> your system. Use, dissemination, distribution, or reproduction of
> this
> > > >> transmission by unintended recipients is not authorized and may be
> > > unlawful.
> > > >>
> > > >>
> > > >
> > >
> >
>
Re: 3.1 Release
Posted by Lorin Beer <lo...@gmail.com>.
I was away a good chunk of yesterday due to a sick wife, getting BB tagged
today. Sorry for the delay.
On Thu, Sep 19, 2013 at 9:59 AM, Shazron <sh...@gmail.com> wrote:
> Sorry for the iOS release guys I'm getting it out today
>
>
> On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <mm...@chromium.org> wrote:
>
> > Specifically, I think the section "Branch & Tag RC1 for Platform
> > Repositories"
> >
> >
> > On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> > > I think its this one: http://wiki.apache.org/cordova/CuttingReleases
> > >
> > >
> > > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> > jheifetz@blackberry.com>wrote:
> > >
> > >> I can take the responsibility of tagging BlackBerry. Could you send me
> > >> the wiki with instructions ?
> > >>
> > >> From: Andrew Grieve <agrieve@chromium.org<mailto:agrieve@chromium.org
> >>
> > >> Date: Thursday, 19 September, 2013 10:40 AM
> > >> To: dev <de...@cordova.apache.org>>,
> > Jeffrey
> > >> Heifetz <jh...@blackberry.com>>
> > >> Subject: Re: 3.1 Release
> > >>
> > >> +Jeffrey - maybe you could take on the BlackBerry component for this
> > >> release?
> > >>
> > >>
> > >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
> > >> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>> wrote:
> > >> Once the platforms are tagged, I can handle the docs. I'll need to
> > review
> > >> our release process and see how the docs can best abide by them.
> > >>
> > >>
> > >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <agrieve@chromium.org
> > >> <ma...@chromium.org>> wrote:
> > >>
> > >> > Shaz - Thanks for the update :). If iOS is the last one then I'd say
> > >> let's
> > >> > go without, but maybe keep at it until we get BB tagged? (just my
> > >> opinion)
> > >> >
> > >> > Heading home now - anyone know if Lorin is away or not?
> > >> >
> > >> >
> > >> > On Wed, Sep 18, 2013 at 3:35 PM, Shazron <shazron@gmail.com<mailto:
> > >> shazron@gmail.com>> wrote:
> > >> >
> > >> > > When i mean ios-deploy still works, it _installs_ it on the
> device,
> > >> but
> > >> > > does _not_ run it.
> > >> > >
> > >> > >
> > >> > > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <shazron@gmail.com
> > <mailto:
> > >> shazron@gmail.com>> wrote:
> > >> > >
> > >> > >> I'm 99% done with iOS specific fixes. One last one I'm trying to
> do
> > >> is
> > >> > >> ios-deploy with lldb:
> > https://issues.apache.org/jira/browse/CB-4804
> > >> > >>
> > >> > >> This means if I don't get this fix in, we _can_ deploy from the
> > >> command
> > >> > >> line using ios-deploy _but_ we can't attach to the debugger. Will
> > >> that
> > >> > be
> > >> > >> acceptable you think?
> > >> > >>
> > >> > >>
> > >> > >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <
> > >> agrieve@chromium.org<ma...@chromium.org>
> > >> > >wrote:
> > >> > >>
> > >> > >>> Ping Lorin & Shaz.
> > >> > >>>
> > >> > >>>
> > >> > >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <
> > >> stevengill97@gmail.com<ma...@gmail.com>
> > >> > >wrote:
> > >> > >>>
> > >> > >>>> FFOS will be tagged tomorrow. I have a few changes I am going
> to
> > >> get
> > >> > in
> > >> > >>>> tomorrow before tagging but it will be good to go very soon!
> > >> > >>>>
> > >> > >>>> With FFOS, Only two plugins have been ported so far (vibration
> > and
> > >> > >>>> device).
> > >> > >>>> We are going to continue to add firefoxos support to plugins
> post
> > >> > >>>> release.
> > >> > >>>> I don't think we should start officially promoting support for
> > FFOS
> > >> > >>>> until
> > >> > >>>> we have more plugins. For 3.1, it will be available for users
> to
> > >> try
> > >> > >>>> out,
> > >> > >>>> test, give feedback, etc.
> > >> > >>>>
> > >> > >>>> Cheers,
> > >> > >>>> -Steve
> > >> > >>>>
> > >> > >>>>
> > >> > >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <
> > >> agrieve@chromium.org<ma...@chromium.org>>
> > >> > >>>> wrote:
> > >> > >>>>
> > >> > >>>> > Thanks Jesse! Great work on being on top of things. If
> changes
> > >> were
> > >> > >>>> done in
> > >> > >>>> > plugin repos, then those aren't a part of this release
> anyways
> > >> and
> > >> > >>>> will be
> > >> > >>>> > picked up by the RELEASENOTES.md within the plugin repos on
> the
> > >> next
> > >> > >>>> > plugins release.
> > >> > >>>> >
> > >> > >>>> > I think it's up to you if you want to start writing
> > >> RELEASENOTES.md
> > >> > >>>> for
> > >> > >>>> > WP7+8. My thinking was just that doing so would make release
> > >> > >>>> announcements
> > >> > >>>> > easier.
> > >> > >>>> >
> > >> > >>>> > Since WP7 and WP8 are in the same repo, does it make sense to
> > >> have
> > >> > >>>> > different subtasks for their taggings? If so, I'll add it to
> > the
> > >> > >>>> template,
> > >> > >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> > >> > >>>> >
> > >> > >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you
> think
> > >> > you'll
> > >> > >>>> be
> > >> > >>>> > able to tag iOS / OSX soon?
> > >> > >>>> > Lorin - Same question for BB. Will you be able to write an
> > update
> > >> > >>>> script
> > >> > >>>> > for it (CB-4776)
> > >> > >>>> > Steve - Likewise for FF
> > >> > >>>> >
> > >> > >>>> > I'd really like this tagging to be done tomorrow so that we
> can
> > >> test
> > >> > >>>> out
> > >> > >>>> > RC1 using RC1 of CLI.
> > >> > >>>> >
> > >> > >>>> >
> > >> > >>>> >
> > >> > >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <
> > purplecabbage@gmail.com
> > >> <ma...@gmail.com>>
> > >> > >>>> wrote:
> > >> > >>>> >
> > >> > >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> > >> > >>>> > >
> > >> > >>>> > > re: Changelog
> > >> > >>>> > > It is a little more difficult in these cases, and I n'er
> > >> > >>>> volunteered to
> > >> > >>>> > do
> > >> > >>>> > > it, so whatevs
> > >> > >>>> > > - WP7+8 live in one repo, so their changes would need to be
> > >> > demuxed
> > >> > >>>> > > - all the changes for Windows8 have happened in the plugin
> > >> repos,
> > >> > >>>> and
> > >> > >>>> > > cordova-js, so changelog would be empty
> > >> > >>>> > >
> > >> > >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
> > >> > >>>> > >
> > >> > >>>> > >
> > >> > >>>> > >
> > >> > >>>> > >
> > >> > >>>> > > @purplecabbage
> > >> > >>>> > > risingj.com<http://risingj.com>
> > >> > >>>> > >
> > >> > >>>> > >
> > >> > >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
> > >> > >>>> agrieve@chromium.org<ma...@chromium.org>
> > >> > >>>> > > >wrote:
> > >> > >>>> > >
> > >> > >>>> > > > For the last plugin release, I tagged them with the
> > plugin's
> > >> > >>>> version.
> > >> > >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that
> > had
> > >> > >>>> changes
> > >> > >>>> > were
> > >> > >>>> > > > included in the release, so some may still not have any
> > >> release
> > >> > >>>> tags.
> > >> > >>>> > > >
> > >> > >>>> > > >
> > >> > >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> > >> > >>>> > braden@chromium.org<ma...@chromium.org>
> > >> > >>>> > > > >wrote:
> > >> > >>>> > > >
> > >> > >>>> > > > > My understanding is that the plugins are totally
> > >> independent
> > >> > of
> > >> > >>>> > Cordova
> > >> > >>>> > > > > versions, and release on their own
> > >> weekly-at-the-most-frequent
> > >> > >>>> cycle.
> > >> > >>>> > > > >
> > >> > >>>> > > > > They only depend on Cordova versions when they need a
> > >> > >>>> sufficiently
> > >> > >>>> > new
> > >> > >>>> > > > > platform to support some feature (binary bridge, for
> > >> example),
> > >> > >>>> and
> > >> > >>>> > then
> > >> > >>>> > > > > they set <engine> tags appropriately.
> > >> > >>>> > > > >
> > >> > >>>> > > > > Braden
> > >> > >>>> > > > >
> > >> > >>>> > > > >
> > >> > >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
> > >> > >>>> cmarcelk@gmail.com<ma...@gmail.com>>
> > >> > >>>> > > > wrote:
> > >> > >>>> > > > >
> > >> > >>>> > > > > > Will the plugin repos get tagged? If so, do they get
> > >> tagged
> > >> > on
> > >> > >>>> > every
> > >> > >>>> > > > > > weekly cycle, or only when a cadence lines up with a
> > >> weekly
> > >> > >>>> cycle,
> > >> > >>>> > or
> > >> > >>>> > > > > both?
> > >> > >>>> > > > > >
> > >> > >>>> > > > > > I see that StepsForPluginRelease wiki say it will
> > happen,
> > >> > and
> > >> > >>>> the
> > >> > >>>> > > most
> > >> > >>>> > > > > > recent coho looks like it will do it, but I currently
> > see
> > >> > >>>> only tags
> > >> > >>>> > > for
> > >> > >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a
> "weekly"
> > >> tag.
> > >> > >>>> > Thanks!
> > >> > >>>> > > > > >
> > >> > >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> > >> > >>>> agrieve@chromium.org<ma...@chromium.org>>
> > >> > >>>> > > > wrote:
> > >> > >>>> > > > > >
> > >> > >>>> > > > > > > I think it's time to get the ball rolling on this.
> > >> It'll
> > >> > be
> > >> > >>>> the
> > >> > >>>> > > first
> > >> > >>>> > > > > > > release post-3.0, so will likely have a few bumps
> to
> > >> work
> > >> > >>>> > through.
> > >> > >>>> > > > > > >
> > >> > >>>> > > > > > > How about:
> > >> > >>>> > > > > > >
> > >> > >>>> > > > > > > Friday 13th - Create release branches & tag RC of
> all
> > >> > repos
> > >> > >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of
> > >> > changelogs)
> > >> > >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> > >> > >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post
> blog
> > >> post
> > >> > >>>> > > > > > >
> > >> > >>>> > > > > > > The main feature of this release will be
> > >> plugman-registry
> > >> > I
> > >> > >>>> > think.
> > >> > >>>> > > > That
> > >> > >>>> > > > > > > said, since CLI / Plugman aren't tied to cadence
> > >> > releases, I
> > >> > >>>> > think
> > >> > >>>> > > > it's
> > >> > >>>> > > > > > > just cordova-docs that is relevant.
> > >> > >>>> > > > > >
> > >> > >>>> > > > > >
> > >> > >>>> > > > >
> > >> > >>>> > > >
> > >> > >>>> > >
> > >> > >>>> >
> > >> > >>>>
> > >> > >>>
> > >> > >>>
> > >> > >>
> > >> > >
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> This transmission (including any attachments) may contain confidential
> > >> information, privileged material (including material protected by the
> > >> solicitor-client or other applicable privileges), or constitute
> > non-public
> > >> information. Any use of this information by anyone other than the
> > intended
> > >> recipient is prohibited. If you have received this transmission in
> > error,
> > >> please immediately reply to the sender and delete this information
> from
> > >> your system. Use, dissemination, distribution, or reproduction of this
> > >> transmission by unintended recipients is not authorized and may be
> > unlawful.
> > >>
> > >>
> > >
> >
>
Re: 3.1 Release
Posted by Shazron <sh...@gmail.com>.
Sorry for the iOS release guys I'm getting it out today
On Thu, Sep 19, 2013 at 8:00 AM, Michal Mocny <mm...@chromium.org> wrote:
> Specifically, I think the section "Branch & Tag RC1 for Platform
> Repositories"
>
>
> On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <mm...@chromium.org> wrote:
>
> > I think its this one: http://wiki.apache.org/cordova/CuttingReleases
> >
> >
> > On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <
> jheifetz@blackberry.com>wrote:
> >
> >> I can take the responsibility of tagging BlackBerry. Could you send me
> >> the wiki with instructions ?
> >>
> >> From: Andrew Grieve <ag...@chromium.org>>
> >> Date: Thursday, 19 September, 2013 10:40 AM
> >> To: dev <de...@cordova.apache.org>>,
> Jeffrey
> >> Heifetz <jh...@blackberry.com>>
> >> Subject: Re: 3.1 Release
> >>
> >> +Jeffrey - maybe you could take on the BlackBerry component for this
> >> release?
> >>
> >>
> >> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
> >> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>> wrote:
> >> Once the platforms are tagged, I can handle the docs. I'll need to
> review
> >> our release process and see how the docs can best abide by them.
> >>
> >>
> >> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <agrieve@chromium.org
> >> <ma...@chromium.org>> wrote:
> >>
> >> > Shaz - Thanks for the update :). If iOS is the last one then I'd say
> >> let's
> >> > go without, but maybe keep at it until we get BB tagged? (just my
> >> opinion)
> >> >
> >> > Heading home now - anyone know if Lorin is away or not?
> >> >
> >> >
> >> > On Wed, Sep 18, 2013 at 3:35 PM, Shazron <shazron@gmail.com<mailto:
> >> shazron@gmail.com>> wrote:
> >> >
> >> > > When i mean ios-deploy still works, it _installs_ it on the device,
> >> but
> >> > > does _not_ run it.
> >> > >
> >> > >
> >> > > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <shazron@gmail.com
> <mailto:
> >> shazron@gmail.com>> wrote:
> >> > >
> >> > >> I'm 99% done with iOS specific fixes. One last one I'm trying to do
> >> is
> >> > >> ios-deploy with lldb:
> https://issues.apache.org/jira/browse/CB-4804
> >> > >>
> >> > >> This means if I don't get this fix in, we _can_ deploy from the
> >> command
> >> > >> line using ios-deploy _but_ we can't attach to the debugger. Will
> >> that
> >> > be
> >> > >> acceptable you think?
> >> > >>
> >> > >>
> >> > >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <
> >> agrieve@chromium.org<ma...@chromium.org>
> >> > >wrote:
> >> > >>
> >> > >>> Ping Lorin & Shaz.
> >> > >>>
> >> > >>>
> >> > >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <
> >> stevengill97@gmail.com<ma...@gmail.com>
> >> > >wrote:
> >> > >>>
> >> > >>>> FFOS will be tagged tomorrow. I have a few changes I am going to
> >> get
> >> > in
> >> > >>>> tomorrow before tagging but it will be good to go very soon!
> >> > >>>>
> >> > >>>> With FFOS, Only two plugins have been ported so far (vibration
> and
> >> > >>>> device).
> >> > >>>> We are going to continue to add firefoxos support to plugins post
> >> > >>>> release.
> >> > >>>> I don't think we should start officially promoting support for
> FFOS
> >> > >>>> until
> >> > >>>> we have more plugins. For 3.1, it will be available for users to
> >> try
> >> > >>>> out,
> >> > >>>> test, give feedback, etc.
> >> > >>>>
> >> > >>>> Cheers,
> >> > >>>> -Steve
> >> > >>>>
> >> > >>>>
> >> > >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <
> >> agrieve@chromium.org<ma...@chromium.org>>
> >> > >>>> wrote:
> >> > >>>>
> >> > >>>> > Thanks Jesse! Great work on being on top of things. If changes
> >> were
> >> > >>>> done in
> >> > >>>> > plugin repos, then those aren't a part of this release anyways
> >> and
> >> > >>>> will be
> >> > >>>> > picked up by the RELEASENOTES.md within the plugin repos on the
> >> next
> >> > >>>> > plugins release.
> >> > >>>> >
> >> > >>>> > I think it's up to you if you want to start writing
> >> RELEASENOTES.md
> >> > >>>> for
> >> > >>>> > WP7+8. My thinking was just that doing so would make release
> >> > >>>> announcements
> >> > >>>> > easier.
> >> > >>>> >
> >> > >>>> > Since WP7 and WP8 are in the same repo, does it make sense to
> >> have
> >> > >>>> > different subtasks for their taggings? If so, I'll add it to
> the
> >> > >>>> template,
> >> > >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> >> > >>>> >
> >> > >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you think
> >> > you'll
> >> > >>>> be
> >> > >>>> > able to tag iOS / OSX soon?
> >> > >>>> > Lorin - Same question for BB. Will you be able to write an
> update
> >> > >>>> script
> >> > >>>> > for it (CB-4776)
> >> > >>>> > Steve - Likewise for FF
> >> > >>>> >
> >> > >>>> > I'd really like this tagging to be done tomorrow so that we can
> >> test
> >> > >>>> out
> >> > >>>> > RC1 using RC1 of CLI.
> >> > >>>> >
> >> > >>>> >
> >> > >>>> >
> >> > >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <
> purplecabbage@gmail.com
> >> <ma...@gmail.com>>
> >> > >>>> wrote:
> >> > >>>> >
> >> > >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> >> > >>>> > >
> >> > >>>> > > re: Changelog
> >> > >>>> > > It is a little more difficult in these cases, and I n'er
> >> > >>>> volunteered to
> >> > >>>> > do
> >> > >>>> > > it, so whatevs
> >> > >>>> > > - WP7+8 live in one repo, so their changes would need to be
> >> > demuxed
> >> > >>>> > > - all the changes for Windows8 have happened in the plugin
> >> repos,
> >> > >>>> and
> >> > >>>> > > cordova-js, so changelog would be empty
> >> > >>>> > >
> >> > >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
> >> > >>>> > >
> >> > >>>> > >
> >> > >>>> > >
> >> > >>>> > >
> >> > >>>> > > @purplecabbage
> >> > >>>> > > risingj.com<http://risingj.com>
> >> > >>>> > >
> >> > >>>> > >
> >> > >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
> >> > >>>> agrieve@chromium.org<ma...@chromium.org>
> >> > >>>> > > >wrote:
> >> > >>>> > >
> >> > >>>> > > > For the last plugin release, I tagged them with the
> plugin's
> >> > >>>> version.
> >> > >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that
> had
> >> > >>>> changes
> >> > >>>> > were
> >> > >>>> > > > included in the release, so some may still not have any
> >> release
> >> > >>>> tags.
> >> > >>>> > > >
> >> > >>>> > > >
> >> > >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> >> > >>>> > braden@chromium.org<ma...@chromium.org>
> >> > >>>> > > > >wrote:
> >> > >>>> > > >
> >> > >>>> > > > > My understanding is that the plugins are totally
> >> independent
> >> > of
> >> > >>>> > Cordova
> >> > >>>> > > > > versions, and release on their own
> >> weekly-at-the-most-frequent
> >> > >>>> cycle.
> >> > >>>> > > > >
> >> > >>>> > > > > They only depend on Cordova versions when they need a
> >> > >>>> sufficiently
> >> > >>>> > new
> >> > >>>> > > > > platform to support some feature (binary bridge, for
> >> example),
> >> > >>>> and
> >> > >>>> > then
> >> > >>>> > > > > they set <engine> tags appropriately.
> >> > >>>> > > > >
> >> > >>>> > > > > Braden
> >> > >>>> > > > >
> >> > >>>> > > > >
> >> > >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
> >> > >>>> cmarcelk@gmail.com<ma...@gmail.com>>
> >> > >>>> > > > wrote:
> >> > >>>> > > > >
> >> > >>>> > > > > > Will the plugin repos get tagged? If so, do they get
> >> tagged
> >> > on
> >> > >>>> > every
> >> > >>>> > > > > > weekly cycle, or only when a cadence lines up with a
> >> weekly
> >> > >>>> cycle,
> >> > >>>> > or
> >> > >>>> > > > > both?
> >> > >>>> > > > > >
> >> > >>>> > > > > > I see that StepsForPluginRelease wiki say it will
> happen,
> >> > and
> >> > >>>> the
> >> > >>>> > > most
> >> > >>>> > > > > > recent coho looks like it will do it, but I currently
> see
> >> > >>>> only tags
> >> > >>>> > > for
> >> > >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly"
> >> tag.
> >> > >>>> > Thanks!
> >> > >>>> > > > > >
> >> > >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> >> > >>>> agrieve@chromium.org<ma...@chromium.org>>
> >> > >>>> > > > wrote:
> >> > >>>> > > > > >
> >> > >>>> > > > > > > I think it's time to get the ball rolling on this.
> >> It'll
> >> > be
> >> > >>>> the
> >> > >>>> > > first
> >> > >>>> > > > > > > release post-3.0, so will likely have a few bumps to
> >> work
> >> > >>>> > through.
> >> > >>>> > > > > > >
> >> > >>>> > > > > > > How about:
> >> > >>>> > > > > > >
> >> > >>>> > > > > > > Friday 13th - Create release branches & tag RC of all
> >> > repos
> >> > >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of
> >> > changelogs)
> >> > >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> >> > >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog
> >> post
> >> > >>>> > > > > > >
> >> > >>>> > > > > > > The main feature of this release will be
> >> plugman-registry
> >> > I
> >> > >>>> > think.
> >> > >>>> > > > That
> >> > >>>> > > > > > > said, since CLI / Plugman aren't tied to cadence
> >> > releases, I
> >> > >>>> > think
> >> > >>>> > > > it's
> >> > >>>> > > > > > > just cordova-docs that is relevant.
> >> > >>>> > > > > >
> >> > >>>> > > > > >
> >> > >>>> > > > >
> >> > >>>> > > >
> >> > >>>> > >
> >> > >>>> >
> >> > >>>>
> >> > >>>
> >> > >>>
> >> > >>
> >> > >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> This transmission (including any attachments) may contain confidential
> >> information, privileged material (including material protected by the
> >> solicitor-client or other applicable privileges), or constitute
> non-public
> >> information. Any use of this information by anyone other than the
> intended
> >> recipient is prohibited. If you have received this transmission in
> error,
> >> please immediately reply to the sender and delete this information from
> >> your system. Use, dissemination, distribution, or reproduction of this
> >> transmission by unintended recipients is not authorized and may be
> unlawful.
> >>
> >>
> >
>
Re: 3.1 Release
Posted by Michal Mocny <mm...@chromium.org>.
Specifically, I think the section "Branch & Tag RC1 for Platform
Repositories"
On Thu, Sep 19, 2013 at 7:59 AM, Michal Mocny <mm...@chromium.org> wrote:
> I think its this one: http://wiki.apache.org/cordova/CuttingReleases
>
>
> On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <jh...@blackberry.com>wrote:
>
>> I can take the responsibility of tagging BlackBerry. Could you send me
>> the wiki with instructions ?
>>
>> From: Andrew Grieve <ag...@chromium.org>>
>> Date: Thursday, 19 September, 2013 10:40 AM
>> To: dev <de...@cordova.apache.org>>, Jeffrey
>> Heifetz <jh...@blackberry.com>>
>> Subject: Re: 3.1 Release
>>
>> +Jeffrey - maybe you could take on the BlackBerry component for this
>> release?
>>
>>
>> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <
>> michael@michaelbrooks.ca<ma...@michaelbrooks.ca>> wrote:
>> Once the platforms are tagged, I can handle the docs. I'll need to review
>> our release process and see how the docs can best abide by them.
>>
>>
>> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <agrieve@chromium.org
>> <ma...@chromium.org>> wrote:
>>
>> > Shaz - Thanks for the update :). If iOS is the last one then I'd say
>> let's
>> > go without, but maybe keep at it until we get BB tagged? (just my
>> opinion)
>> >
>> > Heading home now - anyone know if Lorin is away or not?
>> >
>> >
>> > On Wed, Sep 18, 2013 at 3:35 PM, Shazron <shazron@gmail.com<mailto:
>> shazron@gmail.com>> wrote:
>> >
>> > > When i mean ios-deploy still works, it _installs_ it on the device,
>> but
>> > > does _not_ run it.
>> > >
>> > >
>> > > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <shazron@gmail.com<mailto:
>> shazron@gmail.com>> wrote:
>> > >
>> > >> I'm 99% done with iOS specific fixes. One last one I'm trying to do
>> is
>> > >> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
>> > >>
>> > >> This means if I don't get this fix in, we _can_ deploy from the
>> command
>> > >> line using ios-deploy _but_ we can't attach to the debugger. Will
>> that
>> > be
>> > >> acceptable you think?
>> > >>
>> > >>
>> > >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <
>> agrieve@chromium.org<ma...@chromium.org>
>> > >wrote:
>> > >>
>> > >>> Ping Lorin & Shaz.
>> > >>>
>> > >>>
>> > >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <
>> stevengill97@gmail.com<ma...@gmail.com>
>> > >wrote:
>> > >>>
>> > >>>> FFOS will be tagged tomorrow. I have a few changes I am going to
>> get
>> > in
>> > >>>> tomorrow before tagging but it will be good to go very soon!
>> > >>>>
>> > >>>> With FFOS, Only two plugins have been ported so far (vibration and
>> > >>>> device).
>> > >>>> We are going to continue to add firefoxos support to plugins post
>> > >>>> release.
>> > >>>> I don't think we should start officially promoting support for FFOS
>> > >>>> until
>> > >>>> we have more plugins. For 3.1, it will be available for users to
>> try
>> > >>>> out,
>> > >>>> test, give feedback, etc.
>> > >>>>
>> > >>>> Cheers,
>> > >>>> -Steve
>> > >>>>
>> > >>>>
>> > >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <
>> agrieve@chromium.org<ma...@chromium.org>>
>> > >>>> wrote:
>> > >>>>
>> > >>>> > Thanks Jesse! Great work on being on top of things. If changes
>> were
>> > >>>> done in
>> > >>>> > plugin repos, then those aren't a part of this release anyways
>> and
>> > >>>> will be
>> > >>>> > picked up by the RELEASENOTES.md within the plugin repos on the
>> next
>> > >>>> > plugins release.
>> > >>>> >
>> > >>>> > I think it's up to you if you want to start writing
>> RELEASENOTES.md
>> > >>>> for
>> > >>>> > WP7+8. My thinking was just that doing so would make release
>> > >>>> announcements
>> > >>>> > easier.
>> > >>>> >
>> > >>>> > Since WP7 and WP8 are in the same repo, does it make sense to
>> have
>> > >>>> > different subtasks for their taggings? If so, I'll add it to the
>> > >>>> template,
>> > >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
>> > >>>> >
>> > >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you think
>> > you'll
>> > >>>> be
>> > >>>> > able to tag iOS / OSX soon?
>> > >>>> > Lorin - Same question for BB. Will you be able to write an update
>> > >>>> script
>> > >>>> > for it (CB-4776)
>> > >>>> > Steve - Likewise for FF
>> > >>>> >
>> > >>>> > I'd really like this tagging to be done tomorrow so that we can
>> test
>> > >>>> out
>> > >>>> > RC1 using RC1 of CLI.
>> > >>>> >
>> > >>>> >
>> > >>>> >
>> > >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <purplecabbage@gmail.com
>> <ma...@gmail.com>>
>> > >>>> wrote:
>> > >>>> >
>> > >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
>> > >>>> > >
>> > >>>> > > re: Changelog
>> > >>>> > > It is a little more difficult in these cases, and I n'er
>> > >>>> volunteered to
>> > >>>> > do
>> > >>>> > > it, so whatevs
>> > >>>> > > - WP7+8 live in one repo, so their changes would need to be
>> > demuxed
>> > >>>> > > - all the changes for Windows8 have happened in the plugin
>> repos,
>> > >>>> and
>> > >>>> > > cordova-js, so changelog would be empty
>> > >>>> > >
>> > >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
>> > >>>> > >
>> > >>>> > >
>> > >>>> > >
>> > >>>> > >
>> > >>>> > > @purplecabbage
>> > >>>> > > risingj.com<http://risingj.com>
>> > >>>> > >
>> > >>>> > >
>> > >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
>> > >>>> agrieve@chromium.org<ma...@chromium.org>
>> > >>>> > > >wrote:
>> > >>>> > >
>> > >>>> > > > For the last plugin release, I tagged them with the plugin's
>> > >>>> version.
>> > >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had
>> > >>>> changes
>> > >>>> > were
>> > >>>> > > > included in the release, so some may still not have any
>> release
>> > >>>> tags.
>> > >>>> > > >
>> > >>>> > > >
>> > >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
>> > >>>> > braden@chromium.org<ma...@chromium.org>
>> > >>>> > > > >wrote:
>> > >>>> > > >
>> > >>>> > > > > My understanding is that the plugins are totally
>> independent
>> > of
>> > >>>> > Cordova
>> > >>>> > > > > versions, and release on their own
>> weekly-at-the-most-frequent
>> > >>>> cycle.
>> > >>>> > > > >
>> > >>>> > > > > They only depend on Cordova versions when they need a
>> > >>>> sufficiently
>> > >>>> > new
>> > >>>> > > > > platform to support some feature (binary bridge, for
>> example),
>> > >>>> and
>> > >>>> > then
>> > >>>> > > > > they set <engine> tags appropriately.
>> > >>>> > > > >
>> > >>>> > > > > Braden
>> > >>>> > > > >
>> > >>>> > > > >
>> > >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
>> > >>>> cmarcelk@gmail.com<ma...@gmail.com>>
>> > >>>> > > > wrote:
>> > >>>> > > > >
>> > >>>> > > > > > Will the plugin repos get tagged? If so, do they get
>> tagged
>> > on
>> > >>>> > every
>> > >>>> > > > > > weekly cycle, or only when a cadence lines up with a
>> weekly
>> > >>>> cycle,
>> > >>>> > or
>> > >>>> > > > > both?
>> > >>>> > > > > >
>> > >>>> > > > > > I see that StepsForPluginRelease wiki say it will happen,
>> > and
>> > >>>> the
>> > >>>> > > most
>> > >>>> > > > > > recent coho looks like it will do it, but I currently see
>> > >>>> only tags
>> > >>>> > > for
>> > >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly"
>> tag.
>> > >>>> > Thanks!
>> > >>>> > > > > >
>> > >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
>> > >>>> agrieve@chromium.org<ma...@chromium.org>>
>> > >>>> > > > wrote:
>> > >>>> > > > > >
>> > >>>> > > > > > > I think it's time to get the ball rolling on this.
>> It'll
>> > be
>> > >>>> the
>> > >>>> > > first
>> > >>>> > > > > > > release post-3.0, so will likely have a few bumps to
>> work
>> > >>>> > through.
>> > >>>> > > > > > >
>> > >>>> > > > > > > How about:
>> > >>>> > > > > > >
>> > >>>> > > > > > > Friday 13th - Create release branches & tag RC of all
>> > repos
>> > >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of
>> > changelogs)
>> > >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
>> > >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog
>> post
>> > >>>> > > > > > >
>> > >>>> > > > > > > The main feature of this release will be
>> plugman-registry
>> > I
>> > >>>> > think.
>> > >>>> > > > That
>> > >>>> > > > > > > said, since CLI / Plugman aren't tied to cadence
>> > releases, I
>> > >>>> > think
>> > >>>> > > > it's
>> > >>>> > > > > > > just cordova-docs that is relevant.
>> > >>>> > > > > >
>> > >>>> > > > > >
>> > >>>> > > > >
>> > >>>> > > >
>> > >>>> > >
>> > >>>> >
>> > >>>>
>> > >>>
>> > >>>
>> > >>
>> > >
>> >
>>
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential
>> information, privileged material (including material protected by the
>> solicitor-client or other applicable privileges), or constitute non-public
>> information. Any use of this information by anyone other than the intended
>> recipient is prohibited. If you have received this transmission in error,
>> please immediately reply to the sender and delete this information from
>> your system. Use, dissemination, distribution, or reproduction of this
>> transmission by unintended recipients is not authorized and may be unlawful.
>>
>>
>
Re: 3.1 Release
Posted by Michal Mocny <mm...@chromium.org>.
I think its this one: http://wiki.apache.org/cordova/CuttingReleases
On Thu, Sep 19, 2013 at 7:52 AM, Jeffrey Heifetz <jh...@blackberry.com>wrote:
> I can take the responsibility of tagging BlackBerry. Could you send me the
> wiki with instructions ?
>
> From: Andrew Grieve <ag...@chromium.org>>
> Date: Thursday, 19 September, 2013 10:40 AM
> To: dev <de...@cordova.apache.org>>, Jeffrey
> Heifetz <jh...@blackberry.com>>
> Subject: Re: 3.1 Release
>
> +Jeffrey - maybe you could take on the BlackBerry component for this
> release?
>
>
> On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <michael@michaelbrooks.ca
> <ma...@michaelbrooks.ca>> wrote:
> Once the platforms are tagged, I can handle the docs. I'll need to review
> our release process and see how the docs can best abide by them.
>
>
> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <agrieve@chromium.org
> <ma...@chromium.org>> wrote:
>
> > Shaz - Thanks for the update :). If iOS is the last one then I'd say
> let's
> > go without, but maybe keep at it until we get BB tagged? (just my
> opinion)
> >
> > Heading home now - anyone know if Lorin is away or not?
> >
> >
> > On Wed, Sep 18, 2013 at 3:35 PM, Shazron <shazron@gmail.com<mailto:
> shazron@gmail.com>> wrote:
> >
> > > When i mean ios-deploy still works, it _installs_ it on the device, but
> > > does _not_ run it.
> > >
> > >
> > > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <shazron@gmail.com<mailto:
> shazron@gmail.com>> wrote:
> > >
> > >> I'm 99% done with iOS specific fixes. One last one I'm trying to do is
> > >> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
> > >>
> > >> This means if I don't get this fix in, we _can_ deploy from the
> command
> > >> line using ios-deploy _but_ we can't attach to the debugger. Will that
> > be
> > >> acceptable you think?
> > >>
> > >>
> > >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <agrieve@chromium.org
> <ma...@chromium.org>
> > >wrote:
> > >>
> > >>> Ping Lorin & Shaz.
> > >>>
> > >>>
> > >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <stevengill97@gmail.com
> <ma...@gmail.com>
> > >wrote:
> > >>>
> > >>>> FFOS will be tagged tomorrow. I have a few changes I am going to get
> > in
> > >>>> tomorrow before tagging but it will be good to go very soon!
> > >>>>
> > >>>> With FFOS, Only two plugins have been ported so far (vibration and
> > >>>> device).
> > >>>> We are going to continue to add firefoxos support to plugins post
> > >>>> release.
> > >>>> I don't think we should start officially promoting support for FFOS
> > >>>> until
> > >>>> we have more plugins. For 3.1, it will be available for users to try
> > >>>> out,
> > >>>> test, give feedback, etc.
> > >>>>
> > >>>> Cheers,
> > >>>> -Steve
> > >>>>
> > >>>>
> > >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <
> agrieve@chromium.org<ma...@chromium.org>>
> > >>>> wrote:
> > >>>>
> > >>>> > Thanks Jesse! Great work on being on top of things. If changes
> were
> > >>>> done in
> > >>>> > plugin repos, then those aren't a part of this release anyways and
> > >>>> will be
> > >>>> > picked up by the RELEASENOTES.md within the plugin repos on the
> next
> > >>>> > plugins release.
> > >>>> >
> > >>>> > I think it's up to you if you want to start writing
> RELEASENOTES.md
> > >>>> for
> > >>>> > WP7+8. My thinking was just that doing so would make release
> > >>>> announcements
> > >>>> > easier.
> > >>>> >
> > >>>> > Since WP7 and WP8 are in the same repo, does it make sense to have
> > >>>> > different subtasks for their taggings? If so, I'll add it to the
> > >>>> template,
> > >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> > >>>> >
> > >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you think
> > you'll
> > >>>> be
> > >>>> > able to tag iOS / OSX soon?
> > >>>> > Lorin - Same question for BB. Will you be able to write an update
> > >>>> script
> > >>>> > for it (CB-4776)
> > >>>> > Steve - Likewise for FF
> > >>>> >
> > >>>> > I'd really like this tagging to be done tomorrow so that we can
> test
> > >>>> out
> > >>>> > RC1 using RC1 of CLI.
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <purplecabbage@gmail.com
> <ma...@gmail.com>>
> > >>>> wrote:
> > >>>> >
> > >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> > >>>> > >
> > >>>> > > re: Changelog
> > >>>> > > It is a little more difficult in these cases, and I n'er
> > >>>> volunteered to
> > >>>> > do
> > >>>> > > it, so whatevs
> > >>>> > > - WP7+8 live in one repo, so their changes would need to be
> > demuxed
> > >>>> > > - all the changes for Windows8 have happened in the plugin
> repos,
> > >>>> and
> > >>>> > > cordova-js, so changelog would be empty
> > >>>> > >
> > >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
> > >>>> > >
> > >>>> > >
> > >>>> > >
> > >>>> > >
> > >>>> > > @purplecabbage
> > >>>> > > risingj.com<http://risingj.com>
> > >>>> > >
> > >>>> > >
> > >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
> > >>>> agrieve@chromium.org<ma...@chromium.org>
> > >>>> > > >wrote:
> > >>>> > >
> > >>>> > > > For the last plugin release, I tagged them with the plugin's
> > >>>> version.
> > >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had
> > >>>> changes
> > >>>> > were
> > >>>> > > > included in the release, so some may still not have any
> release
> > >>>> tags.
> > >>>> > > >
> > >>>> > > >
> > >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> > >>>> > braden@chromium.org<ma...@chromium.org>
> > >>>> > > > >wrote:
> > >>>> > > >
> > >>>> > > > > My understanding is that the plugins are totally independent
> > of
> > >>>> > Cordova
> > >>>> > > > > versions, and release on their own
> weekly-at-the-most-frequent
> > >>>> cycle.
> > >>>> > > > >
> > >>>> > > > > They only depend on Cordova versions when they need a
> > >>>> sufficiently
> > >>>> > new
> > >>>> > > > > platform to support some feature (binary bridge, for
> example),
> > >>>> and
> > >>>> > then
> > >>>> > > > > they set <engine> tags appropriately.
> > >>>> > > > >
> > >>>> > > > > Braden
> > >>>> > > > >
> > >>>> > > > >
> > >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
> > >>>> cmarcelk@gmail.com<ma...@gmail.com>>
> > >>>> > > > wrote:
> > >>>> > > > >
> > >>>> > > > > > Will the plugin repos get tagged? If so, do they get
> tagged
> > on
> > >>>> > every
> > >>>> > > > > > weekly cycle, or only when a cadence lines up with a
> weekly
> > >>>> cycle,
> > >>>> > or
> > >>>> > > > > both?
> > >>>> > > > > >
> > >>>> > > > > > I see that StepsForPluginRelease wiki say it will happen,
> > and
> > >>>> the
> > >>>> > > most
> > >>>> > > > > > recent coho looks like it will do it, but I currently see
> > >>>> only tags
> > >>>> > > for
> > >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly"
> tag.
> > >>>> > Thanks!
> > >>>> > > > > >
> > >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> > >>>> agrieve@chromium.org<ma...@chromium.org>>
> > >>>> > > > wrote:
> > >>>> > > > > >
> > >>>> > > > > > > I think it's time to get the ball rolling on this. It'll
> > be
> > >>>> the
> > >>>> > > first
> > >>>> > > > > > > release post-3.0, so will likely have a few bumps to
> work
> > >>>> > through.
> > >>>> > > > > > >
> > >>>> > > > > > > How about:
> > >>>> > > > > > >
> > >>>> > > > > > > Friday 13th - Create release branches & tag RC of all
> > repos
> > >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of
> > changelogs)
> > >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> > >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog
> post
> > >>>> > > > > > >
> > >>>> > > > > > > The main feature of this release will be
> plugman-registry
> > I
> > >>>> > think.
> > >>>> > > > That
> > >>>> > > > > > > said, since CLI / Plugman aren't tied to cadence
> > releases, I
> > >>>> > think
> > >>>> > > > it's
> > >>>> > > > > > > just cordova-docs that is relevant.
> > >>>> > > > > >
> > >>>> > > > > >
> > >>>> > > > >
> > >>>> > > >
> > >>>> > >
> > >>>> >
> > >>>>
> > >>>
> > >>>
> > >>
> > >
> >
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>
>
Re: 3.1 Release
Posted by Jeffrey Heifetz <jh...@blackberry.com>.
I can take the responsibility of tagging BlackBerry. Could you send me the wiki with instructions ?
From: Andrew Grieve <ag...@chromium.org>>
Date: Thursday, 19 September, 2013 10:40 AM
To: dev <de...@cordova.apache.org>>, Jeffrey Heifetz <jh...@blackberry.com>>
Subject: Re: 3.1 Release
+Jeffrey - maybe you could take on the BlackBerry component for this release?
On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks <mi...@michaelbrooks.ca>> wrote:
Once the platforms are tagged, I can handle the docs. I'll need to review
our release process and see how the docs can best abide by them.
On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <ag...@chromium.org>> wrote:
> Shaz - Thanks for the update :). If iOS is the last one then I'd say let's
> go without, but maybe keep at it until we get BB tagged? (just my opinion)
>
> Heading home now - anyone know if Lorin is away or not?
>
>
> On Wed, Sep 18, 2013 at 3:35 PM, Shazron <sh...@gmail.com>> wrote:
>
> > When i mean ios-deploy still works, it _installs_ it on the device, but
> > does _not_ run it.
> >
> >
> > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <sh...@gmail.com>> wrote:
> >
> >> I'm 99% done with iOS specific fixes. One last one I'm trying to do is
> >> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
> >>
> >> This means if I don't get this fix in, we _can_ deploy from the command
> >> line using ios-deploy _but_ we can't attach to the debugger. Will that
> be
> >> acceptable you think?
> >>
> >>
> >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <ag...@chromium.org>
> >wrote:
> >>
> >>> Ping Lorin & Shaz.
> >>>
> >>>
> >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <st...@gmail.com>
> >wrote:
> >>>
> >>>> FFOS will be tagged tomorrow. I have a few changes I am going to get
> in
> >>>> tomorrow before tagging but it will be good to go very soon!
> >>>>
> >>>> With FFOS, Only two plugins have been ported so far (vibration and
> >>>> device).
> >>>> We are going to continue to add firefoxos support to plugins post
> >>>> release.
> >>>> I don't think we should start officially promoting support for FFOS
> >>>> until
> >>>> we have more plugins. For 3.1, it will be available for users to try
> >>>> out,
> >>>> test, give feedback, etc.
> >>>>
> >>>> Cheers,
> >>>> -Steve
> >>>>
> >>>>
> >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <ag...@chromium.org>>
> >>>> wrote:
> >>>>
> >>>> > Thanks Jesse! Great work on being on top of things. If changes were
> >>>> done in
> >>>> > plugin repos, then those aren't a part of this release anyways and
> >>>> will be
> >>>> > picked up by the RELEASENOTES.md within the plugin repos on the next
> >>>> > plugins release.
> >>>> >
> >>>> > I think it's up to you if you want to start writing RELEASENOTES.md
> >>>> for
> >>>> > WP7+8. My thinking was just that doing so would make release
> >>>> announcements
> >>>> > easier.
> >>>> >
> >>>> > Since WP7 and WP8 are in the same repo, does it make sense to have
> >>>> > different subtasks for their taggings? If so, I'll add it to the
> >>>> template,
> >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> >>>> >
> >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you think
> you'll
> >>>> be
> >>>> > able to tag iOS / OSX soon?
> >>>> > Lorin - Same question for BB. Will you be able to write an update
> >>>> script
> >>>> > for it (CB-4776)
> >>>> > Steve - Likewise for FF
> >>>> >
> >>>> > I'd really like this tagging to be done tomorrow so that we can test
> >>>> out
> >>>> > RC1 using RC1 of CLI.
> >>>> >
> >>>> >
> >>>> >
> >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com>>
> >>>> wrote:
> >>>> >
> >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> >>>> > >
> >>>> > > re: Changelog
> >>>> > > It is a little more difficult in these cases, and I n'er
> >>>> volunteered to
> >>>> > do
> >>>> > > it, so whatevs
> >>>> > > - WP7+8 live in one repo, so their changes would need to be
> demuxed
> >>>> > > - all the changes for Windows8 have happened in the plugin repos,
> >>>> and
> >>>> > > cordova-js, so changelog would be empty
> >>>> > >
> >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> > > @purplecabbage
> >>>> > > risingj.com<http://risingj.com>
> >>>> > >
> >>>> > >
> >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
> >>>> agrieve@chromium.org<ma...@chromium.org>
> >>>> > > >wrote:
> >>>> > >
> >>>> > > > For the last plugin release, I tagged them with the plugin's
> >>>> version.
> >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had
> >>>> changes
> >>>> > were
> >>>> > > > included in the release, so some may still not have any release
> >>>> tags.
> >>>> > > >
> >>>> > > >
> >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> >>>> > braden@chromium.org<ma...@chromium.org>
> >>>> > > > >wrote:
> >>>> > > >
> >>>> > > > > My understanding is that the plugins are totally independent
> of
> >>>> > Cordova
> >>>> > > > > versions, and release on their own weekly-at-the-most-frequent
> >>>> cycle.
> >>>> > > > >
> >>>> > > > > They only depend on Cordova versions when they need a
> >>>> sufficiently
> >>>> > new
> >>>> > > > > platform to support some feature (binary bridge, for example),
> >>>> and
> >>>> > then
> >>>> > > > > they set <engine> tags appropriately.
> >>>> > > > >
> >>>> > > > > Braden
> >>>> > > > >
> >>>> > > > >
> >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
> >>>> cmarcelk@gmail.com<ma...@gmail.com>>
> >>>> > > > wrote:
> >>>> > > > >
> >>>> > > > > > Will the plugin repos get tagged? If so, do they get tagged
> on
> >>>> > every
> >>>> > > > > > weekly cycle, or only when a cadence lines up with a weekly
> >>>> cycle,
> >>>> > or
> >>>> > > > > both?
> >>>> > > > > >
> >>>> > > > > > I see that StepsForPluginRelease wiki say it will happen,
> and
> >>>> the
> >>>> > > most
> >>>> > > > > > recent coho looks like it will do it, but I currently see
> >>>> only tags
> >>>> > > for
> >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag.
> >>>> > Thanks!
> >>>> > > > > >
> >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> >>>> agrieve@chromium.org<ma...@chromium.org>>
> >>>> > > > wrote:
> >>>> > > > > >
> >>>> > > > > > > I think it's time to get the ball rolling on this. It'll
> be
> >>>> the
> >>>> > > first
> >>>> > > > > > > release post-3.0, so will likely have a few bumps to work
> >>>> > through.
> >>>> > > > > > >
> >>>> > > > > > > How about:
> >>>> > > > > > >
> >>>> > > > > > > Friday 13th - Create release branches & tag RC of all
> repos
> >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of
> changelogs)
> >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>>> > > > > > >
> >>>> > > > > > > The main feature of this release will be plugman-registry
> I
> >>>> > think.
> >>>> > > > That
> >>>> > > > > > > said, since CLI / Plugman aren't tied to cadence
> releases, I
> >>>> > think
> >>>> > > > it's
> >>>> > > > > > > just cordova-docs that is relevant.
> >>>> > > > > >
> >>>> > > > > >
> >>>> > > > >
> >>>> > > >
> >>>> > >
> >>>> >
> >>>>
> >>>
> >>>
> >>
> >
>
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
+Jeffrey - maybe you could take on the BlackBerry component for this
release?
On Thu, Sep 19, 2013 at 10:00 AM, Michael Brooks
<mi...@michaelbrooks.ca>wrote:
> Once the platforms are tagged, I can handle the docs. I'll need to review
> our release process and see how the docs can best abide by them.
>
>
> On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Shaz - Thanks for the update :). If iOS is the last one then I'd say
> let's
> > go without, but maybe keep at it until we get BB tagged? (just my
> opinion)
> >
> > Heading home now - anyone know if Lorin is away or not?
> >
> >
> > On Wed, Sep 18, 2013 at 3:35 PM, Shazron <sh...@gmail.com> wrote:
> >
> > > When i mean ios-deploy still works, it _installs_ it on the device, but
> > > does _not_ run it.
> > >
> > >
> > > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <sh...@gmail.com> wrote:
> > >
> > >> I'm 99% done with iOS specific fixes. One last one I'm trying to do is
> > >> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
> > >>
> > >> This means if I don't get this fix in, we _can_ deploy from the
> command
> > >> line using ios-deploy _but_ we can't attach to the debugger. Will that
> > be
> > >> acceptable you think?
> > >>
> > >>
> > >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <agrieve@chromium.org
> > >wrote:
> > >>
> > >>> Ping Lorin & Shaz.
> > >>>
> > >>>
> > >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <stevengill97@gmail.com
> > >wrote:
> > >>>
> > >>>> FFOS will be tagged tomorrow. I have a few changes I am going to get
> > in
> > >>>> tomorrow before tagging but it will be good to go very soon!
> > >>>>
> > >>>> With FFOS, Only two plugins have been ported so far (vibration and
> > >>>> device).
> > >>>> We are going to continue to add firefoxos support to plugins post
> > >>>> release.
> > >>>> I don't think we should start officially promoting support for FFOS
> > >>>> until
> > >>>> we have more plugins. For 3.1, it will be available for users to try
> > >>>> out,
> > >>>> test, give feedback, etc.
> > >>>>
> > >>>> Cheers,
> > >>>> -Steve
> > >>>>
> > >>>>
> > >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <
> agrieve@chromium.org>
> > >>>> wrote:
> > >>>>
> > >>>> > Thanks Jesse! Great work on being on top of things. If changes
> were
> > >>>> done in
> > >>>> > plugin repos, then those aren't a part of this release anyways and
> > >>>> will be
> > >>>> > picked up by the RELEASENOTES.md within the plugin repos on the
> next
> > >>>> > plugins release.
> > >>>> >
> > >>>> > I think it's up to you if you want to start writing
> RELEASENOTES.md
> > >>>> for
> > >>>> > WP7+8. My thinking was just that doing so would make release
> > >>>> announcements
> > >>>> > easier.
> > >>>> >
> > >>>> > Since WP7 and WP8 are in the same repo, does it make sense to have
> > >>>> > different subtasks for their taggings? If so, I'll add it to the
> > >>>> template,
> > >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> > >>>> >
> > >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you think
> > you'll
> > >>>> be
> > >>>> > able to tag iOS / OSX soon?
> > >>>> > Lorin - Same question for BB. Will you be able to write an update
> > >>>> script
> > >>>> > for it (CB-4776)
> > >>>> > Steve - Likewise for FF
> > >>>> >
> > >>>> > I'd really like this tagging to be done tomorrow so that we can
> test
> > >>>> out
> > >>>> > RC1 using RC1 of CLI.
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com>
> > >>>> wrote:
> > >>>> >
> > >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> > >>>> > >
> > >>>> > > re: Changelog
> > >>>> > > It is a little more difficult in these cases, and I n'er
> > >>>> volunteered to
> > >>>> > do
> > >>>> > > it, so whatevs
> > >>>> > > - WP7+8 live in one repo, so their changes would need to be
> > demuxed
> > >>>> > > - all the changes for Windows8 have happened in the plugin
> repos,
> > >>>> and
> > >>>> > > cordova-js, so changelog would be empty
> > >>>> > >
> > >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
> > >>>> > >
> > >>>> > >
> > >>>> > >
> > >>>> > >
> > >>>> > > @purplecabbage
> > >>>> > > risingj.com
> > >>>> > >
> > >>>> > >
> > >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
> > >>>> agrieve@chromium.org
> > >>>> > > >wrote:
> > >>>> > >
> > >>>> > > > For the last plugin release, I tagged them with the plugin's
> > >>>> version.
> > >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had
> > >>>> changes
> > >>>> > were
> > >>>> > > > included in the release, so some may still not have any
> release
> > >>>> tags.
> > >>>> > > >
> > >>>> > > >
> > >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> > >>>> > braden@chromium.org
> > >>>> > > > >wrote:
> > >>>> > > >
> > >>>> > > > > My understanding is that the plugins are totally independent
> > of
> > >>>> > Cordova
> > >>>> > > > > versions, and release on their own
> weekly-at-the-most-frequent
> > >>>> cycle.
> > >>>> > > > >
> > >>>> > > > > They only depend on Cordova versions when they need a
> > >>>> sufficiently
> > >>>> > new
> > >>>> > > > > platform to support some feature (binary bridge, for
> example),
> > >>>> and
> > >>>> > then
> > >>>> > > > > they set <engine> tags appropriately.
> > >>>> > > > >
> > >>>> > > > > Braden
> > >>>> > > > >
> > >>>> > > > >
> > >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
> > >>>> cmarcelk@gmail.com>
> > >>>> > > > wrote:
> > >>>> > > > >
> > >>>> > > > > > Will the plugin repos get tagged? If so, do they get
> tagged
> > on
> > >>>> > every
> > >>>> > > > > > weekly cycle, or only when a cadence lines up with a
> weekly
> > >>>> cycle,
> > >>>> > or
> > >>>> > > > > both?
> > >>>> > > > > >
> > >>>> > > > > > I see that StepsForPluginRelease wiki say it will happen,
> > and
> > >>>> the
> > >>>> > > most
> > >>>> > > > > > recent coho looks like it will do it, but I currently see
> > >>>> only tags
> > >>>> > > for
> > >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly"
> tag.
> > >>>> > Thanks!
> > >>>> > > > > >
> > >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> > >>>> agrieve@chromium.org>
> > >>>> > > > wrote:
> > >>>> > > > > >
> > >>>> > > > > > > I think it's time to get the ball rolling on this. It'll
> > be
> > >>>> the
> > >>>> > > first
> > >>>> > > > > > > release post-3.0, so will likely have a few bumps to
> work
> > >>>> > through.
> > >>>> > > > > > >
> > >>>> > > > > > > How about:
> > >>>> > > > > > >
> > >>>> > > > > > > Friday 13th - Create release branches & tag RC of all
> > repos
> > >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of
> > changelogs)
> > >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> > >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog
> post
> > >>>> > > > > > >
> > >>>> > > > > > > The main feature of this release will be
> plugman-registry
> > I
> > >>>> > think.
> > >>>> > > > That
> > >>>> > > > > > > said, since CLI / Plugman aren't tied to cadence
> > releases, I
> > >>>> > think
> > >>>> > > > it's
> > >>>> > > > > > > just cordova-docs that is relevant.
> > >>>> > > > > >
> > >>>> > > > > >
> > >>>> > > > >
> > >>>> > > >
> > >>>> > >
> > >>>> >
> > >>>>
> > >>>
> > >>>
> > >>
> > >
> >
>
Re: 3.1 Release
Posted by Michael Brooks <mi...@michaelbrooks.ca>.
Once the platforms are tagged, I can handle the docs. I'll need to review
our release process and see how the docs can best abide by them.
On Wed, Sep 18, 2013 at 1:34 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Shaz - Thanks for the update :). If iOS is the last one then I'd say let's
> go without, but maybe keep at it until we get BB tagged? (just my opinion)
>
> Heading home now - anyone know if Lorin is away or not?
>
>
> On Wed, Sep 18, 2013 at 3:35 PM, Shazron <sh...@gmail.com> wrote:
>
> > When i mean ios-deploy still works, it _installs_ it on the device, but
> > does _not_ run it.
> >
> >
> > On Wed, Sep 18, 2013 at 12:31 PM, Shazron <sh...@gmail.com> wrote:
> >
> >> I'm 99% done with iOS specific fixes. One last one I'm trying to do is
> >> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
> >>
> >> This means if I don't get this fix in, we _can_ deploy from the command
> >> line using ios-deploy _but_ we can't attach to the debugger. Will that
> be
> >> acceptable you think?
> >>
> >>
> >> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <agrieve@chromium.org
> >wrote:
> >>
> >>> Ping Lorin & Shaz.
> >>>
> >>>
> >>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <stevengill97@gmail.com
> >wrote:
> >>>
> >>>> FFOS will be tagged tomorrow. I have a few changes I am going to get
> in
> >>>> tomorrow before tagging but it will be good to go very soon!
> >>>>
> >>>> With FFOS, Only two plugins have been ported so far (vibration and
> >>>> device).
> >>>> We are going to continue to add firefoxos support to plugins post
> >>>> release.
> >>>> I don't think we should start officially promoting support for FFOS
> >>>> until
> >>>> we have more plugins. For 3.1, it will be available for users to try
> >>>> out,
> >>>> test, give feedback, etc.
> >>>>
> >>>> Cheers,
> >>>> -Steve
> >>>>
> >>>>
> >>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <ag...@chromium.org>
> >>>> wrote:
> >>>>
> >>>> > Thanks Jesse! Great work on being on top of things. If changes were
> >>>> done in
> >>>> > plugin repos, then those aren't a part of this release anyways and
> >>>> will be
> >>>> > picked up by the RELEASENOTES.md within the plugin repos on the next
> >>>> > plugins release.
> >>>> >
> >>>> > I think it's up to you if you want to start writing RELEASENOTES.md
> >>>> for
> >>>> > WP7+8. My thinking was just that doing so would make release
> >>>> announcements
> >>>> > easier.
> >>>> >
> >>>> > Since WP7 and WP8 are in the same repo, does it make sense to have
> >>>> > different subtasks for their taggings? If so, I'll add it to the
> >>>> template,
> >>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> >>>> >
> >>>> > Shaz - I see you're still checking in iOS7 fixes. Do you think
> you'll
> >>>> be
> >>>> > able to tag iOS / OSX soon?
> >>>> > Lorin - Same question for BB. Will you be able to write an update
> >>>> script
> >>>> > for it (CB-4776)
> >>>> > Steve - Likewise for FF
> >>>> >
> >>>> > I'd really like this tagging to be done tomorrow so that we can test
> >>>> out
> >>>> > RC1 using RC1 of CLI.
> >>>> >
> >>>> >
> >>>> >
> >>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com>
> >>>> wrote:
> >>>> >
> >>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> >>>> > >
> >>>> > > re: Changelog
> >>>> > > It is a little more difficult in these cases, and I n'er
> >>>> volunteered to
> >>>> > do
> >>>> > > it, so whatevs
> >>>> > > - WP7+8 live in one repo, so their changes would need to be
> demuxed
> >>>> > > - all the changes for Windows8 have happened in the plugin repos,
> >>>> and
> >>>> > > cordova-js, so changelog would be empty
> >>>> > >
> >>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> > > @purplecabbage
> >>>> > > risingj.com
> >>>> > >
> >>>> > >
> >>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
> >>>> agrieve@chromium.org
> >>>> > > >wrote:
> >>>> > >
> >>>> > > > For the last plugin release, I tagged them with the plugin's
> >>>> version.
> >>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had
> >>>> changes
> >>>> > were
> >>>> > > > included in the release, so some may still not have any release
> >>>> tags.
> >>>> > > >
> >>>> > > >
> >>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> >>>> > braden@chromium.org
> >>>> > > > >wrote:
> >>>> > > >
> >>>> > > > > My understanding is that the plugins are totally independent
> of
> >>>> > Cordova
> >>>> > > > > versions, and release on their own weekly-at-the-most-frequent
> >>>> cycle.
> >>>> > > > >
> >>>> > > > > They only depend on Cordova versions when they need a
> >>>> sufficiently
> >>>> > new
> >>>> > > > > platform to support some feature (binary bridge, for example),
> >>>> and
> >>>> > then
> >>>> > > > > they set <engine> tags appropriately.
> >>>> > > > >
> >>>> > > > > Braden
> >>>> > > > >
> >>>> > > > >
> >>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
> >>>> cmarcelk@gmail.com>
> >>>> > > > wrote:
> >>>> > > > >
> >>>> > > > > > Will the plugin repos get tagged? If so, do they get tagged
> on
> >>>> > every
> >>>> > > > > > weekly cycle, or only when a cadence lines up with a weekly
> >>>> cycle,
> >>>> > or
> >>>> > > > > both?
> >>>> > > > > >
> >>>> > > > > > I see that StepsForPluginRelease wiki say it will happen,
> and
> >>>> the
> >>>> > > most
> >>>> > > > > > recent coho looks like it will do it, but I currently see
> >>>> only tags
> >>>> > > for
> >>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag.
> >>>> > Thanks!
> >>>> > > > > >
> >>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
> >>>> agrieve@chromium.org>
> >>>> > > > wrote:
> >>>> > > > > >
> >>>> > > > > > > I think it's time to get the ball rolling on this. It'll
> be
> >>>> the
> >>>> > > first
> >>>> > > > > > > release post-3.0, so will likely have a few bumps to work
> >>>> > through.
> >>>> > > > > > >
> >>>> > > > > > > How about:
> >>>> > > > > > >
> >>>> > > > > > > Friday 13th - Create release branches & tag RC of all
> repos
> >>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of
> changelogs)
> >>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> >>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >>>> > > > > > >
> >>>> > > > > > > The main feature of this release will be plugman-registry
> I
> >>>> > think.
> >>>> > > > That
> >>>> > > > > > > said, since CLI / Plugman aren't tied to cadence
> releases, I
> >>>> > think
> >>>> > > > it's
> >>>> > > > > > > just cordova-docs that is relevant.
> >>>> > > > > >
> >>>> > > > > >
> >>>> > > > >
> >>>> > > >
> >>>> > >
> >>>> >
> >>>>
> >>>
> >>>
> >>
> >
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Shaz - Thanks for the update :). If iOS is the last one then I'd say let's
go without, but maybe keep at it until we get BB tagged? (just my opinion)
Heading home now - anyone know if Lorin is away or not?
On Wed, Sep 18, 2013 at 3:35 PM, Shazron <sh...@gmail.com> wrote:
> When i mean ios-deploy still works, it _installs_ it on the device, but
> does _not_ run it.
>
>
> On Wed, Sep 18, 2013 at 12:31 PM, Shazron <sh...@gmail.com> wrote:
>
>> I'm 99% done with iOS specific fixes. One last one I'm trying to do is
>> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
>>
>> This means if I don't get this fix in, we _can_ deploy from the command
>> line using ios-deploy _but_ we can't attach to the debugger. Will that be
>> acceptable you think?
>>
>>
>> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <ag...@chromium.org>wrote:
>>
>>> Ping Lorin & Shaz.
>>>
>>>
>>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <st...@gmail.com>wrote:
>>>
>>>> FFOS will be tagged tomorrow. I have a few changes I am going to get in
>>>> tomorrow before tagging but it will be good to go very soon!
>>>>
>>>> With FFOS, Only two plugins have been ported so far (vibration and
>>>> device).
>>>> We are going to continue to add firefoxos support to plugins post
>>>> release.
>>>> I don't think we should start officially promoting support for FFOS
>>>> until
>>>> we have more plugins. For 3.1, it will be available for users to try
>>>> out,
>>>> test, give feedback, etc.
>>>>
>>>> Cheers,
>>>> -Steve
>>>>
>>>>
>>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <ag...@chromium.org>
>>>> wrote:
>>>>
>>>> > Thanks Jesse! Great work on being on top of things. If changes were
>>>> done in
>>>> > plugin repos, then those aren't a part of this release anyways and
>>>> will be
>>>> > picked up by the RELEASENOTES.md within the plugin repos on the next
>>>> > plugins release.
>>>> >
>>>> > I think it's up to you if you want to start writing RELEASENOTES.md
>>>> for
>>>> > WP7+8. My thinking was just that doing so would make release
>>>> announcements
>>>> > easier.
>>>> >
>>>> > Since WP7 and WP8 are in the same repo, does it make sense to have
>>>> > different subtasks for their taggings? If so, I'll add it to the
>>>> template,
>>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
>>>> >
>>>> > Shaz - I see you're still checking in iOS7 fixes. Do you think you'll
>>>> be
>>>> > able to tag iOS / OSX soon?
>>>> > Lorin - Same question for BB. Will you be able to write an update
>>>> script
>>>> > for it (CB-4776)
>>>> > Steve - Likewise for FF
>>>> >
>>>> > I'd really like this tagging to be done tomorrow so that we can test
>>>> out
>>>> > RC1 using RC1 of CLI.
>>>> >
>>>> >
>>>> >
>>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com>
>>>> wrote:
>>>> >
>>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
>>>> > >
>>>> > > re: Changelog
>>>> > > It is a little more difficult in these cases, and I n'er
>>>> volunteered to
>>>> > do
>>>> > > it, so whatevs
>>>> > > - WP7+8 live in one repo, so their changes would need to be demuxed
>>>> > > - all the changes for Windows8 have happened in the plugin repos,
>>>> and
>>>> > > cordova-js, so changelog would be empty
>>>> > >
>>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
>>>> > >
>>>> > >
>>>> > >
>>>> > >
>>>> > > @purplecabbage
>>>> > > risingj.com
>>>> > >
>>>> > >
>>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
>>>> agrieve@chromium.org
>>>> > > >wrote:
>>>> > >
>>>> > > > For the last plugin release, I tagged them with the plugin's
>>>> version.
>>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had
>>>> changes
>>>> > were
>>>> > > > included in the release, so some may still not have any release
>>>> tags.
>>>> > > >
>>>> > > >
>>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
>>>> > braden@chromium.org
>>>> > > > >wrote:
>>>> > > >
>>>> > > > > My understanding is that the plugins are totally independent of
>>>> > Cordova
>>>> > > > > versions, and release on their own weekly-at-the-most-frequent
>>>> cycle.
>>>> > > > >
>>>> > > > > They only depend on Cordova versions when they need a
>>>> sufficiently
>>>> > new
>>>> > > > > platform to support some feature (binary bridge, for example),
>>>> and
>>>> > then
>>>> > > > > they set <engine> tags appropriately.
>>>> > > > >
>>>> > > > > Braden
>>>> > > > >
>>>> > > > >
>>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
>>>> cmarcelk@gmail.com>
>>>> > > > wrote:
>>>> > > > >
>>>> > > > > > Will the plugin repos get tagged? If so, do they get tagged on
>>>> > every
>>>> > > > > > weekly cycle, or only when a cadence lines up with a weekly
>>>> cycle,
>>>> > or
>>>> > > > > both?
>>>> > > > > >
>>>> > > > > > I see that StepsForPluginRelease wiki say it will happen, and
>>>> the
>>>> > > most
>>>> > > > > > recent coho looks like it will do it, but I currently see
>>>> only tags
>>>> > > for
>>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag.
>>>> > Thanks!
>>>> > > > > >
>>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
>>>> agrieve@chromium.org>
>>>> > > > wrote:
>>>> > > > > >
>>>> > > > > > > I think it's time to get the ball rolling on this. It'll be
>>>> the
>>>> > > first
>>>> > > > > > > release post-3.0, so will likely have a few bumps to work
>>>> > through.
>>>> > > > > > >
>>>> > > > > > > How about:
>>>> > > > > > >
>>>> > > > > > > Friday 13th - Create release branches & tag RC of all repos
>>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of changelogs)
>>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
>>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>>> > > > > > >
>>>> > > > > > > The main feature of this release will be plugman-registry I
>>>> > think.
>>>> > > > That
>>>> > > > > > > said, since CLI / Plugman aren't tied to cadence releases, I
>>>> > think
>>>> > > > it's
>>>> > > > > > > just cordova-docs that is relevant.
>>>> > > > > >
>>>> > > > > >
>>>> > > > >
>>>> > > >
>>>> > >
>>>> >
>>>>
>>>
>>>
>>
>
Re: 3.1 Release
Posted by Shazron <sh...@gmail.com>.
When i mean ios-deploy still works, it _installs_ it on the device, but
does _not_ run it.
On Wed, Sep 18, 2013 at 12:31 PM, Shazron <sh...@gmail.com> wrote:
> I'm 99% done with iOS specific fixes. One last one I'm trying to do is
> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
>
> This means if I don't get this fix in, we _can_ deploy from the command
> line using ios-deploy _but_ we can't attach to the debugger. Will that be
> acceptable you think?
>
>
> On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <ag...@chromium.org>wrote:
>
>> Ping Lorin & Shaz.
>>
>>
>> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <st...@gmail.com>wrote:
>>
>>> FFOS will be tagged tomorrow. I have a few changes I am going to get in
>>> tomorrow before tagging but it will be good to go very soon!
>>>
>>> With FFOS, Only two plugins have been ported so far (vibration and
>>> device).
>>> We are going to continue to add firefoxos support to plugins post
>>> release.
>>> I don't think we should start officially promoting support for FFOS until
>>> we have more plugins. For 3.1, it will be available for users to try out,
>>> test, give feedback, etc.
>>>
>>> Cheers,
>>> -Steve
>>>
>>>
>>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <ag...@chromium.org>
>>> wrote:
>>>
>>> > Thanks Jesse! Great work on being on top of things. If changes were
>>> done in
>>> > plugin repos, then those aren't a part of this release anyways and
>>> will be
>>> > picked up by the RELEASENOTES.md within the plugin repos on the next
>>> > plugins release.
>>> >
>>> > I think it's up to you if you want to start writing RELEASENOTES.md for
>>> > WP7+8. My thinking was just that doing so would make release
>>> announcements
>>> > easier.
>>> >
>>> > Since WP7 and WP8 are in the same repo, does it make sense to have
>>> > different subtasks for their taggings? If so, I'll add it to the
>>> template,
>>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
>>> >
>>> > Shaz - I see you're still checking in iOS7 fixes. Do you think you'll
>>> be
>>> > able to tag iOS / OSX soon?
>>> > Lorin - Same question for BB. Will you be able to write an update
>>> script
>>> > for it (CB-4776)
>>> > Steve - Likewise for FF
>>> >
>>> > I'd really like this tagging to be done tomorrow so that we can test
>>> out
>>> > RC1 using RC1 of CLI.
>>> >
>>> >
>>> >
>>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com>
>>> wrote:
>>> >
>>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
>>> > >
>>> > > re: Changelog
>>> > > It is a little more difficult in these cases, and I n'er volunteered
>>> to
>>> > do
>>> > > it, so whatevs
>>> > > - WP7+8 live in one repo, so their changes would need to be demuxed
>>> > > - all the changes for Windows8 have happened in the plugin repos, and
>>> > > cordova-js, so changelog would be empty
>>> > >
>>> > > Maybe I'll get this together for the 3.1.0, we'll see.
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > @purplecabbage
>>> > > risingj.com
>>> > >
>>> > >
>>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <
>>> agrieve@chromium.org
>>> > > >wrote:
>>> > >
>>> > > > For the last plugin release, I tagged them with the plugin's
>>> version.
>>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had
>>> changes
>>> > were
>>> > > > included in the release, so some may still not have any release
>>> tags.
>>> > > >
>>> > > >
>>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
>>> > braden@chromium.org
>>> > > > >wrote:
>>> > > >
>>> > > > > My understanding is that the plugins are totally independent of
>>> > Cordova
>>> > > > > versions, and release on their own weekly-at-the-most-frequent
>>> cycle.
>>> > > > >
>>> > > > > They only depend on Cordova versions when they need a
>>> sufficiently
>>> > new
>>> > > > > platform to support some feature (binary bridge, for example),
>>> and
>>> > then
>>> > > > > they set <engine> tags appropriately.
>>> > > > >
>>> > > > > Braden
>>> > > > >
>>> > > > >
>>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
>>> cmarcelk@gmail.com>
>>> > > > wrote:
>>> > > > >
>>> > > > > > Will the plugin repos get tagged? If so, do they get tagged on
>>> > every
>>> > > > > > weekly cycle, or only when a cadence lines up with a weekly
>>> cycle,
>>> > or
>>> > > > > both?
>>> > > > > >
>>> > > > > > I see that StepsForPluginRelease wiki say it will happen, and
>>> the
>>> > > most
>>> > > > > > recent coho looks like it will do it, but I currently see only
>>> tags
>>> > > for
>>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag.
>>> > Thanks!
>>> > > > > >
>>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
>>> agrieve@chromium.org>
>>> > > > wrote:
>>> > > > > >
>>> > > > > > > I think it's time to get the ball rolling on this. It'll be
>>> the
>>> > > first
>>> > > > > > > release post-3.0, so will likely have a few bumps to work
>>> > through.
>>> > > > > > >
>>> > > > > > > How about:
>>> > > > > > >
>>> > > > > > > Friday 13th - Create release branches & tag RC of all repos
>>> > > > > > > Monday 16th - Draft Release Blog Post (digest of changelogs)
>>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
>>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>>> > > > > > >
>>> > > > > > > The main feature of this release will be plugman-registry I
>>> > think.
>>> > > > That
>>> > > > > > > said, since CLI / Plugman aren't tied to cadence releases, I
>>> > think
>>> > > > it's
>>> > > > > > > just cordova-docs that is relevant.
>>> > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>
Re: 3.1 Release
Posted by Shazron <sh...@gmail.com>.
I'm 99% done with iOS specific fixes. One last one I'm trying to do is
ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
This means if I don't get this fix in, we _can_ deploy from the command
line using ios-deploy _but_ we can't attach to the debugger. Will that be
acceptable you think?
On Wed, Sep 18, 2013 at 12:07 PM, Andrew Grieve <ag...@chromium.org>wrote:
> Ping Lorin & Shaz.
>
>
> On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <st...@gmail.com>wrote:
>
>> FFOS will be tagged tomorrow. I have a few changes I am going to get in
>> tomorrow before tagging but it will be good to go very soon!
>>
>> With FFOS, Only two plugins have been ported so far (vibration and
>> device).
>> We are going to continue to add firefoxos support to plugins post release.
>> I don't think we should start officially promoting support for FFOS until
>> we have more plugins. For 3.1, it will be available for users to try out,
>> test, give feedback, etc.
>>
>> Cheers,
>> -Steve
>>
>>
>> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <ag...@chromium.org>
>> wrote:
>>
>> > Thanks Jesse! Great work on being on top of things. If changes were
>> done in
>> > plugin repos, then those aren't a part of this release anyways and will
>> be
>> > picked up by the RELEASENOTES.md within the plugin repos on the next
>> > plugins release.
>> >
>> > I think it's up to you if you want to start writing RELEASENOTES.md for
>> > WP7+8. My thinking was just that doing so would make release
>> announcements
>> > easier.
>> >
>> > Since WP7 and WP8 are in the same repo, does it make sense to have
>> > different subtasks for their taggings? If so, I'll add it to the
>> template,
>> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
>> >
>> > Shaz - I see you're still checking in iOS7 fixes. Do you think you'll be
>> > able to tag iOS / OSX soon?
>> > Lorin - Same question for BB. Will you be able to write an update script
>> > for it (CB-4776)
>> > Steve - Likewise for FF
>> >
>> > I'd really like this tagging to be done tomorrow so that we can test out
>> > RC1 using RC1 of CLI.
>> >
>> >
>> >
>> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com>
>> wrote:
>> >
>> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
>> > >
>> > > re: Changelog
>> > > It is a little more difficult in these cases, and I n'er volunteered
>> to
>> > do
>> > > it, so whatevs
>> > > - WP7+8 live in one repo, so their changes would need to be demuxed
>> > > - all the changes for Windows8 have happened in the plugin repos, and
>> > > cordova-js, so changelog would be empty
>> > >
>> > > Maybe I'll get this together for the 3.1.0, we'll see.
>> > >
>> > >
>> > >
>> > >
>> > > @purplecabbage
>> > > risingj.com
>> > >
>> > >
>> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <agrieve@chromium.org
>> > > >wrote:
>> > >
>> > > > For the last plugin release, I tagged them with the plugin's
>> version.
>> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had changes
>> > were
>> > > > included in the release, so some may still not have any release
>> tags.
>> > > >
>> > > >
>> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
>> > braden@chromium.org
>> > > > >wrote:
>> > > >
>> > > > > My understanding is that the plugins are totally independent of
>> > Cordova
>> > > > > versions, and release on their own weekly-at-the-most-frequent
>> cycle.
>> > > > >
>> > > > > They only depend on Cordova versions when they need a sufficiently
>> > new
>> > > > > platform to support some feature (binary bridge, for example), and
>> > then
>> > > > > they set <engine> tags appropriately.
>> > > > >
>> > > > > Braden
>> > > > >
>> > > > >
>> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <
>> cmarcelk@gmail.com>
>> > > > wrote:
>> > > > >
>> > > > > > Will the plugin repos get tagged? If so, do they get tagged on
>> > every
>> > > > > > weekly cycle, or only when a cadence lines up with a weekly
>> cycle,
>> > or
>> > > > > both?
>> > > > > >
>> > > > > > I see that StepsForPluginRelease wiki say it will happen, and
>> the
>> > > most
>> > > > > > recent coho looks like it will do it, but I currently see only
>> tags
>> > > for
>> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag.
>> > Thanks!
>> > > > > >
>> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <
>> agrieve@chromium.org>
>> > > > wrote:
>> > > > > >
>> > > > > > > I think it's time to get the ball rolling on this. It'll be
>> the
>> > > first
>> > > > > > > release post-3.0, so will likely have a few bumps to work
>> > through.
>> > > > > > >
>> > > > > > > How about:
>> > > > > > >
>> > > > > > > Friday 13th - Create release branches & tag RC of all repos
>> > > > > > > Monday 16th - Draft Release Blog Post (digest of changelogs)
>> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
>> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>> > > > > > >
>> > > > > > > The main feature of this release will be plugman-registry I
>> > think.
>> > > > That
>> > > > > > > said, since CLI / Plugman aren't tied to cadence releases, I
>> > think
>> > > > it's
>> > > > > > > just cordova-docs that is relevant.
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Ping Lorin & Shaz.
On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill <st...@gmail.com> wrote:
> FFOS will be tagged tomorrow. I have a few changes I am going to get in
> tomorrow before tagging but it will be good to go very soon!
>
> With FFOS, Only two plugins have been ported so far (vibration and device).
> We are going to continue to add firefoxos support to plugins post release.
> I don't think we should start officially promoting support for FFOS until
> we have more plugins. For 3.1, it will be available for users to try out,
> test, give feedback, etc.
>
> Cheers,
> -Steve
>
>
> On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Thanks Jesse! Great work on being on top of things. If changes were done
> in
> > plugin repos, then those aren't a part of this release anyways and will
> be
> > picked up by the RELEASENOTES.md within the plugin repos on the next
> > plugins release.
> >
> > I think it's up to you if you want to start writing RELEASENOTES.md for
> > WP7+8. My thinking was just that doing so would make release
> announcements
> > easier.
> >
> > Since WP7 and WP8 are in the same repo, does it make sense to have
> > different subtasks for their taggings? If so, I'll add it to the
> template,
> > if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
> >
> > Shaz - I see you're still checking in iOS7 fixes. Do you think you'll be
> > able to tag iOS / OSX soon?
> > Lorin - Same question for BB. Will you be able to write an update script
> > for it (CB-4776)
> > Steve - Likewise for FF
> >
> > I'd really like this tagging to be done tomorrow so that we can test out
> > RC1 using RC1 of CLI.
> >
> >
> >
> > On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> > >
> > > re: Changelog
> > > It is a little more difficult in these cases, and I n'er volunteered to
> > do
> > > it, so whatevs
> > > - WP7+8 live in one repo, so their changes would need to be demuxed
> > > - all the changes for Windows8 have happened in the plugin repos, and
> > > cordova-js, so changelog would be empty
> > >
> > > Maybe I'll get this together for the 3.1.0, we'll see.
> > >
> > >
> > >
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > >
> > > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <agrieve@chromium.org
> > > >wrote:
> > >
> > > > For the last plugin release, I tagged them with the plugin's version.
> > > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had changes
> > were
> > > > included in the release, so some may still not have any release tags.
> > > >
> > > >
> > > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> > braden@chromium.org
> > > > >wrote:
> > > >
> > > > > My understanding is that the plugins are totally independent of
> > Cordova
> > > > > versions, and release on their own weekly-at-the-most-frequent
> cycle.
> > > > >
> > > > > They only depend on Cordova versions when they need a sufficiently
> > new
> > > > > platform to support some feature (binary bridge, for example), and
> > then
> > > > > they set <engine> tags appropriately.
> > > > >
> > > > > Braden
> > > > >
> > > > >
> > > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <cmarcelk@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Will the plugin repos get tagged? If so, do they get tagged on
> > every
> > > > > > weekly cycle, or only when a cadence lines up with a weekly
> cycle,
> > or
> > > > > both?
> > > > > >
> > > > > > I see that StepsForPluginRelease wiki say it will happen, and the
> > > most
> > > > > > recent coho looks like it will do it, but I currently see only
> tags
> > > for
> > > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag.
> > Thanks!
> > > > > >
> > > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <agrieve@chromium.org
> >
> > > > wrote:
> > > > > >
> > > > > > > I think it's time to get the ball rolling on this. It'll be the
> > > first
> > > > > > > release post-3.0, so will likely have a few bumps to work
> > through.
> > > > > > >
> > > > > > > How about:
> > > > > > >
> > > > > > > Friday 13th - Create release branches & tag RC of all repos
> > > > > > > Monday 16th - Draft Release Blog Post (digest of changelogs)
> > > > > > > Thurs 19th - Tag 3.1.0 for all repos
> > > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> > > > > > >
> > > > > > > The main feature of this release will be plugman-registry I
> > think.
> > > > That
> > > > > > > said, since CLI / Plugman aren't tied to cadence releases, I
> > think
> > > > it's
> > > > > > > just cordova-docs that is relevant.
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: 3.1 Release
Posted by Steven Gill <st...@gmail.com>.
FFOS will be tagged tomorrow. I have a few changes I am going to get in
tomorrow before tagging but it will be good to go very soon!
With FFOS, Only two plugins have been ported so far (vibration and device).
We are going to continue to add firefoxos support to plugins post release.
I don't think we should start officially promoting support for FFOS until
we have more plugins. For 3.1, it will be available for users to try out,
test, give feedback, etc.
Cheers,
-Steve
On Tue, Sep 17, 2013 at 7:38 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Thanks Jesse! Great work on being on top of things. If changes were done in
> plugin repos, then those aren't a part of this release anyways and will be
> picked up by the RELEASENOTES.md within the plugin repos on the next
> plugins release.
>
> I think it's up to you if you want to start writing RELEASENOTES.md for
> WP7+8. My thinking was just that doing so would make release announcements
> easier.
>
> Since WP7 and WP8 are in the same repo, does it make sense to have
> different subtasks for their taggings? If so, I'll add it to the template,
> if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
>
> Shaz - I see you're still checking in iOS7 fixes. Do you think you'll be
> able to tag iOS / OSX soon?
> Lorin - Same question for BB. Will you be able to write an update script
> for it (CB-4776)
> Steve - Likewise for FF
>
> I'd really like this tagging to be done tomorrow so that we can test out
> RC1 using RC1 of CLI.
>
>
>
> On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com> wrote:
>
> > WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
> >
> > re: Changelog
> > It is a little more difficult in these cases, and I n'er volunteered to
> do
> > it, so whatevs
> > - WP7+8 live in one repo, so their changes would need to be demuxed
> > - all the changes for Windows8 have happened in the plugin repos, and
> > cordova-js, so changelog would be empty
> >
> > Maybe I'll get this together for the 3.1.0, we'll see.
> >
> >
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <agrieve@chromium.org
> > >wrote:
> >
> > > For the last plugin release, I tagged them with the plugin's version.
> > > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had changes
> were
> > > included in the release, so some may still not have any release tags.
> > >
> > >
> > > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <
> braden@chromium.org
> > > >wrote:
> > >
> > > > My understanding is that the plugins are totally independent of
> Cordova
> > > > versions, and release on their own weekly-at-the-most-frequent cycle.
> > > >
> > > > They only depend on Cordova versions when they need a sufficiently
> new
> > > > platform to support some feature (binary bridge, for example), and
> then
> > > > they set <engine> tags appropriately.
> > > >
> > > > Braden
> > > >
> > > >
> > > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <cm...@gmail.com>
> > > wrote:
> > > >
> > > > > Will the plugin repos get tagged? If so, do they get tagged on
> every
> > > > > weekly cycle, or only when a cadence lines up with a weekly cycle,
> or
> > > > both?
> > > > >
> > > > > I see that StepsForPluginRelease wiki say it will happen, and the
> > most
> > > > > recent coho looks like it will do it, but I currently see only tags
> > for
> > > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag.
> Thanks!
> > > > >
> > > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > > > >
> > > > > > I think it's time to get the ball rolling on this. It'll be the
> > first
> > > > > > release post-3.0, so will likely have a few bumps to work
> through.
> > > > > >
> > > > > > How about:
> > > > > >
> > > > > > Friday 13th - Create release branches & tag RC of all repos
> > > > > > Monday 16th - Draft Release Blog Post (digest of changelogs)
> > > > > > Thurs 19th - Tag 3.1.0 for all repos
> > > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> > > > > >
> > > > > > The main feature of this release will be plugman-registry I
> think.
> > > That
> > > > > > said, since CLI / Plugman aren't tied to cadence releases, I
> think
> > > it's
> > > > > > just cordova-docs that is relevant.
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
Thanks Jesse! Great work on being on top of things. If changes were done in
plugin repos, then those aren't a part of this release anyways and will be
picked up by the RELEASENOTES.md within the plugin repos on the next
plugins release.
I think it's up to you if you want to start writing RELEASENOTES.md for
WP7+8. My thinking was just that doing so would make release announcements
easier.
Since WP7 and WP8 are in the same repo, does it make sense to have
different subtasks for their taggings? If so, I'll add it to the template,
if not, maybe I'll just change WP8 to say WP7+WP8? WDYT?
Shaz - I see you're still checking in iOS7 fixes. Do you think you'll be
able to tag iOS / OSX soon?
Lorin - Same question for BB. Will you be able to write an update script
for it (CB-4776)
Steve - Likewise for FF
I'd really like this tagging to be done tomorrow so that we can test out
RC1 using RC1 of CLI.
On Tue, Sep 17, 2013 at 10:00 PM, Jesse <pu...@gmail.com> wrote:
> WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
>
> re: Changelog
> It is a little more difficult in these cases, and I n'er volunteered to do
> it, so whatevs
> - WP7+8 live in one repo, so their changes would need to be demuxed
> - all the changes for Windows8 have happened in the plugin repos, and
> cordova-js, so changelog would be empty
>
> Maybe I'll get this together for the 3.1.0, we'll see.
>
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > For the last plugin release, I tagged them with the plugin's version.
> > (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had changes were
> > included in the release, so some may still not have any release tags.
> >
> >
> > On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <braden@chromium.org
> > >wrote:
> >
> > > My understanding is that the plugins are totally independent of Cordova
> > > versions, and release on their own weekly-at-the-most-frequent cycle.
> > >
> > > They only depend on Cordova versions when they need a sufficiently new
> > > platform to support some feature (binary bridge, for example), and then
> > > they set <engine> tags appropriately.
> > >
> > > Braden
> > >
> > >
> > > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <cm...@gmail.com>
> > wrote:
> > >
> > > > Will the plugin repos get tagged? If so, do they get tagged on every
> > > > weekly cycle, or only when a cadence lines up with a weekly cycle, or
> > > both?
> > > >
> > > > I see that StepsForPluginRelease wiki say it will happen, and the
> most
> > > > recent coho looks like it will do it, but I currently see only tags
> for
> > > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag. Thanks!
> > > >
> > > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> > > >
> > > > > I think it's time to get the ball rolling on this. It'll be the
> first
> > > > > release post-3.0, so will likely have a few bumps to work through.
> > > > >
> > > > > How about:
> > > > >
> > > > > Friday 13th - Create release branches & tag RC of all repos
> > > > > Monday 16th - Draft Release Blog Post (digest of changelogs)
> > > > > Thurs 19th - Tag 3.1.0 for all repos
> > > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> > > > >
> > > > > The main feature of this release will be plugman-registry I think.
> > That
> > > > > said, since CLI / Plugman aren't tied to cadence releases, I think
> > it's
> > > > > just cordova-docs that is relevant.
> > > >
> > > >
> > >
> >
>
Re: 3.1 Release
Posted by Jesse <pu...@gmail.com>.
WP7, WP8, and Windows8 are all tagged 3.1.0-rc1
re: Changelog
It is a little more difficult in these cases, and I n'er volunteered to do
it, so whatevs
- WP7+8 live in one repo, so their changes would need to be demuxed
- all the changes for Windows8 have happened in the plugin repos, and
cordova-js, so changelog would be empty
Maybe I'll get this together for the 3.1.0, we'll see.
@purplecabbage
risingj.com
On Tue, Sep 17, 2013 at 12:34 PM, Andrew Grieve <ag...@chromium.org>wrote:
> For the last plugin release, I tagged them with the plugin's version.
> (e.g. r0.2.1 for cordova-plugin-file). Only plugins that had changes were
> included in the release, so some may still not have any release tags.
>
>
> On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <braden@chromium.org
> >wrote:
>
> > My understanding is that the plugins are totally independent of Cordova
> > versions, and release on their own weekly-at-the-most-frequent cycle.
> >
> > They only depend on Cordova versions when they need a sufficiently new
> > platform to support some feature (binary bridge, for example), and then
> > they set <engine> tags appropriately.
> >
> > Braden
> >
> >
> > On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <cm...@gmail.com>
> wrote:
> >
> > > Will the plugin repos get tagged? If so, do they get tagged on every
> > > weekly cycle, or only when a cadence lines up with a weekly cycle, or
> > both?
> > >
> > > I see that StepsForPluginRelease wiki say it will happen, and the most
> > > recent coho looks like it will do it, but I currently see only tags for
> > > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag. Thanks!
> > >
> > > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
> > >
> > > > I think it's time to get the ball rolling on this. It'll be the first
> > > > release post-3.0, so will likely have a few bumps to work through.
> > > >
> > > > How about:
> > > >
> > > > Friday 13th - Create release branches & tag RC of all repos
> > > > Monday 16th - Draft Release Blog Post (digest of changelogs)
> > > > Thurs 19th - Tag 3.1.0 for all repos
> > > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> > > >
> > > > The main feature of this release will be plugman-registry I think.
> That
> > > > said, since CLI / Plugman aren't tied to cadence releases, I think
> it's
> > > > just cordova-docs that is relevant.
> > >
> > >
> >
>
Re: 3.1 Release
Posted by Andrew Grieve <ag...@chromium.org>.
For the last plugin release, I tagged them with the plugin's version.
(e.g. r0.2.1 for cordova-plugin-file). Only plugins that had changes were
included in the release, so some may still not have any release tags.
On Tue, Sep 17, 2013 at 3:31 PM, Braden Shepherdson <br...@chromium.org>wrote:
> My understanding is that the plugins are totally independent of Cordova
> versions, and release on their own weekly-at-the-most-frequent cycle.
>
> They only depend on Cordova versions when they need a sufficiently new
> platform to support some feature (binary bridge, for example), and then
> they set <engine> tags appropriately.
>
> Braden
>
>
> On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > Will the plugin repos get tagged? If so, do they get tagged on every
> > weekly cycle, or only when a cadence lines up with a weekly cycle, or
> both?
> >
> > I see that StepsForPluginRelease wiki say it will happen, and the most
> > recent coho looks like it will do it, but I currently see only tags for
> > 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag. Thanks!
> >
> > On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org> wrote:
> >
> > > I think it's time to get the ball rolling on this. It'll be the first
> > > release post-3.0, so will likely have a few bumps to work through.
> > >
> > > How about:
> > >
> > > Friday 13th - Create release branches & tag RC of all repos
> > > Monday 16th - Draft Release Blog Post (digest of changelogs)
> > > Thurs 19th - Tag 3.1.0 for all repos
> > > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> > >
> > > The main feature of this release will be plugman-registry I think. That
> > > said, since CLI / Plugman aren't tied to cadence releases, I think it's
> > > just cordova-docs that is relevant.
> >
> >
>
Re: 3.1 Release
Posted by Braden Shepherdson <br...@chromium.org>.
My understanding is that the plugins are totally independent of Cordova
versions, and release on their own weekly-at-the-most-frequent cycle.
They only depend on Cordova versions when they need a sufficiently new
platform to support some feature (binary bridge, for example), and then
they set <engine> tags appropriately.
Braden
On Tue, Sep 17, 2013 at 3:18 PM, Marcel Kinard <cm...@gmail.com> wrote:
> Will the plugin repos get tagged? If so, do they get tagged on every
> weekly cycle, or only when a cadence lines up with a weekly cycle, or both?
>
> I see that StepsForPluginRelease wiki say it will happen, and the most
> recent coho looks like it will do it, but I currently see only tags for
> 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag. Thanks!
>
> On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org> wrote:
>
> > I think it's time to get the ball rolling on this. It'll be the first
> > release post-3.0, so will likely have a few bumps to work through.
> >
> > How about:
> >
> > Friday 13th - Create release branches & tag RC of all repos
> > Monday 16th - Draft Release Blog Post (digest of changelogs)
> > Thurs 19th - Tag 3.1.0 for all repos
> > Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
> >
> > The main feature of this release will be plugman-registry I think. That
> > said, since CLI / Plugman aren't tied to cadence releases, I think it's
> > just cordova-docs that is relevant.
>
>
Re: 3.1 Release
Posted by Marcel Kinard <cm...@gmail.com>.
Will the plugin repos get tagged? If so, do they get tagged on every weekly cycle, or only when a cadence lines up with a weekly cycle, or both?
I see that StepsForPluginRelease wiki say it will happen, and the most recent coho looks like it will do it, but I currently see only tags for 3.0.0 and 3.0.0rc1 in the plugins repos, not a "weekly" tag. Thanks!
On Sep 9, 2013, at 10:42 AM, Andrew Grieve <ag...@chromium.org> wrote:
> I think it's time to get the ball rolling on this. It'll be the first
> release post-3.0, so will likely have a few bumps to work through.
>
> How about:
>
> Friday 13th - Create release branches & tag RC of all repos
> Monday 16th - Draft Release Blog Post (digest of changelogs)
> Thurs 19th - Tag 3.1.0 for all repos
> Fri 20th - Push 3.1.0-1.0.0 of CLI to npm & Post blog post
>
> The main feature of this release will be plugman-registry I think. That
> said, since CLI / Plugman aren't tied to cadence releases, I think it's
> just cordova-docs that is relevant.