Quoting Kate Stewart (kate.stew...@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
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.
T
On 16/05/12 09:34, James Page wrote:
One feature that is currently lacking in the whiteboard is the ability
to track changes over time (although you could do this through
diligent monitoring of blueprint email spam). Its possible that we
might start managing the whiteboard content in a bzr bran
James Page wrote:
> [...]
> I think that this approach did not work that well - often the spec did
> not get updated throughout the cycle as the primary focus is normally
> on work item tracking in the blueprint - so they age and become pretty
> useless very quickly.
>
> That said there are a few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Team
I've spent some time with various members of the Ubuntu Server Team
over the last few weeks reviewing how we use blueprints to track
progress during the development cycle.
This was really with the objective of trying to resolve a few
challe
