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 cmarcelk@gmail.com designates
 209.85.212.50 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: 3.1 Release
From: Marcel Kinard <cmarcelk@gmail.com>
In-Reply-To: 
 <CABiQX1UvYSrMy3OtkPkbn4tjZZoM0d4SSuxWZO9eO43C8OEB7w@mail.gmail.com>
Date: Tue, 17 Sep 2013 15:18:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <002154C8-322E-4CD0-B1F2-B02C1222BCC1@gmail.com>
References: 
 <CABiQX1UvYSrMy3OtkPkbn4tjZZoM0d4SSuxWZO9eO43C8OEB7w@mail.gmail.com>
To: dev@cordova.apache.org

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.
>=20
> How about:
>=20
> 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
>=20
> 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.