linaro-project-management team mailing list archive

[Christian Robottom Reis <kiko@xxxxxxxxxx>]

On Tue, Sep 06, 2011 at 01:29:14PM +0200, Alexander Sack wrote:
> so a while back me and fabo discussed using blueprints to burn down the
> "standard" release monthly release and develop a default template that would
> be instantiated for each and every month. If you look at the
> project-management project you can see the current instance there.

I assume you mean

    https://launchpad.net/linaro-project-management/+milestone/2011.09

> For that fabo will create a template and initial blueprint instances for the
> two key PM events during the month: planning and post-mortem; we feel that
> this has been managed a bit lax in the past and fabo currently has to do
> quite a few manual pokings etc. and we think having those blueprints will
> help better track progress.

I"m not sure exactly what you mean here -- I see 3 blueprints for l-p-m
which I think are relevant:

    https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-11.09-release-tracking
    https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-11.09-gather-proposed-headlines
    https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-11.09-release-response-team-tracking

I think you're suggesting something a bit different for the actual
engineering teams, though. Is there an example blueprint we can see that
explains how this will work?

> Driving delivery of those blueprints will be worked into the overall release
> blueprint for now. Later we probably will make one more standalone blueprint
> to drive those two very important phases.

I don't know what you mean in this piece :-/
-- 
Christian Robottom Reis, Engineering VP
Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935
Linaro.org: Open Source Software for ARM SoCs