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 <agri...@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 <rstew...@adobe.com> wrote: > >> Ahh, thanks for the info. Any ETA on the updated plugins? >> >> =Ryan >> >> On 9/20/13 1:46 PM, "Michal Mocny" <mmo...@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 <rstew...@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" <stevengil...@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 <cmarc...@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 <agri...@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 <agri...@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 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>
