Use of Blueprints + Blueprint Template

[Serge Hallyn]

Quoting Kate Stewart (kate.stewart at canonical.com):
> 
> On Wed, 2012-05-16 at 09:34 +0100, James Page wrote:
> > That said there are a few concepts in the specification template that
> > I think would still benefit our use of blueprints.  So I'd like to
> > propose bringing in some of the concepts we had in specs to the
> > blueprint summary and whiteboard.
> 
> Thanks for pulling this together James,  it fits nicely into our need to
> automate away a lot of the mindless manual part of tracking the release.
> I've gone ahead and created a WIKI page to summarize your template [1],
> and will be starting off a wider discussion on this beyond the server
> team.  We've got too many half followed ways of tracking the status of
> features [2][3][4], and until we standardize, automation isn't going to
> happen effectively.  
> 
> Thierry's points are valid about the lack of history on the whiteboard
> section,  but folks can subscribe to the blueprints they're interested
> in and monitor, so I don't consider this a blocker.  Certainly its

For now I'm just using lp:~serge-hallyn/+junk/blueprints-q to track
my changes, so right, if i see nonsense changes in email i can trivially
revert.

-serge