blueprint priorities

Andy Whitcroft apw at
Wed May 25 10:13:28 UTC 2011

On Wed, May 25, 2011 at 06:45:28AM +0200, Martin Pitt wrote:
> Hello Allison,
> Allison Randal [2011-05-24 15:03 -0700]:
> > Essential - Must happen in this cycle
> > High - Desirable in this cycle
> > Medium - Would like to happen in this cycle
> > Low - Likely to be dropped from this cycle
> That's how the desktop team uses them as well, roughly. I. e. >= High
> → we'll invest significant resources to make it happen, Medium → we
> want it, but if something goes wrong we won't hesitate much to defer,
> and low is entirely a target of opportunity.

There kernel team is about the same.  Essential must happen, typically
these blueprint carry items without which there is no kernel.  High we
really really want, but there will be a kernel without.  Medium we want
but if theres no time, drop me.  Low, if we run out of things to do,
then these.


More information about the ubuntu-devel mailing list