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 <bra...@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 <cmarc...@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 <agri...@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. > > > > >
