Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of purplecabbage@gmail.com
 designates 209.85.212.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOBL_k5Ox0L4rnedc1O8uQP=ArPppvibCQZC_KY3kpqCBP9r9g@mail.gmail.com>
References: 
 <CAEeF2TeeF3d=Cyxouutphx-QVozWah=N7=r+SZWUkKvKLHNE-Q@mail.gmail.com>
	<CE6202B1.49A36%rstewart@adobe.com>
	<CABiQX1WX5VG0_-9BOZ1gwXqF-2=bXgdGz-wCmWNPGz84XPwQGQ@mail.gmail.com>
	<CANpVHHxMMksDzkmcUyLBPEwVDJcf3pwV+s=xiGkhr7iLK8wASQ@mail.gmail.com>
	<CANpVHHzP1b7AvjdfxOPmBt-MebDoFYQ7o0H1qTg7wYcWYRxt2Q@mail.gmail.com>
	<CAMk5LLmcqBc5EUdNSLVpkJQ90BC9r1d17hzOCys_s5uSOKpsTQ@mail.gmail.com>
	<CAOBL_k5Ox0L4rnedc1O8uQP=ArPppvibCQZC_KY3kpqCBP9r9g@mail.gmail.com>
Date: Mon, 23 Sep 2013 13:37:41 -0700
Message-ID: 
 <CAKP6k2v3r1=Xi7D9MX8BE-5wX9_cNDwHszkF3nLo4hfjK=X4LA@mail.gmail.com>
Subject: Re: 3.1 Release
From: Jesse <purplecabbage@gmail.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>, bowserj@apache.org
Content-Type: multipart/alternative; boundary=047d7b6dc9c6e7cfee04e712fd9e

--047d7b6dc9c6e7cfee04e712fd9e
Content-Type: text/plain; charset=ISO-8859-1

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 <bowserj@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 <anis.kadri@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 <anis.kadri@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 <rstewart@adobe.com>
> >> wrote:
> >> >>
> >> >>> Ahh, thanks for the info. Any ETA on the updated plugins?
> >> >>>
> >> >>> =Ryan
> >> >>>
> >> >>> On 9/20/13 1:46 PM, "Michal Mocny" <mmocny@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" <stevengill97@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
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >>
> >> >>> >>
> >> >>>
> >> >>>
> >>
>

--047d7b6dc9c6e7cfee04e712fd9e--