Monthly component release candidate dates

Jamie Bennett jamie.bennett at
Wed Mar 2 11:55:15 UTC 2011

On 02/03/11 at 09:52pm, Michael Hope wrote:
> On Wed, Mar 2, 2011 at 9:48 PM, Peter Maydell <peter.maydell at> wrote:
> > On 2 March 2011 01:33, Michael Hope <michael.hope at> wrote:
> >> On Wed, Mar 2, 2011 at 10:04 AM, Peter Maydell <peter.maydell at> wrote:
> >>>>> >
> >
> >>> That would be an annoying format change for toolchain group
> >>> releases, which are already on a monthly schedule and currently
> >>> use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...)
> >>> for release versions.
> >
> >> Hi Peter.  We'll keep the 2011.xx-y names for the products.  Each
> >> project has product series and a planning series.  The product series
> >> are ones like '4.5' or '4.4' for gcc-linaro, and 'trunk' for
> >> qemu-linaro, and these then have milestones like '2011.03'.
> >
> > Is this a proposal to vary the proposed new milestone names,
> > or a suggestion that the toolchain group should continue as
> > it is and not worry about the inconsistency with other groups?
> There's no change from our product series/milestone naming point of
> view.  The dates will change to the end of the month to sync up across
> Linaro.  There will be a parallel and, unfortunately, largely
> identical planning series with milestones as well.

For to correctly track your Blueprints and Work Items
together with the rest of Linaro's outputs they must be targeted to a
milestone named like in the wiki page. Status will group all projects
together with the same milestone to get a picture of what is due for
that date. Targeting Work Items or Blueprints to another milestone will
mean they won't show up.

> -- Michael


More information about the linaro-dev mailing list