micro release exception for bzr

[Mark Shuttleworth]

 On 17/09/10 08:19, Martin Pool wrote:
> The criteria for
> changes to our stable branches are intended to match the criteria for
> Ubuntu updates, so if they don't match we can certainly consider
> changing them.  In particular fixes to the stable branch, unless there
> is an compelling reason:
>
>  * must not change APIs
>  * must not change default formats or interoperability
>  * should have a Launchpad bug number
>  * should have a reasonably small patch,
>  * should not have gratuitous code cleanups or rearrangements
>  * should add new tests for fixed bugs
>  * should be careful of anything that may change cross-platform behaviour
>

That looks SRU-compatible to me.

> We have a pretty substantial test suite (about 26,000 tests) which is
> run on every release-branch commit, and we require new tests for bug
> fixes or features if it is at all practical.  I believe the tests are
> currently done during upstream releases rather than during package
> builds, but I see no reason why they couldn't be turned on there.
>

I'd rather require a manual test run confirmation before the archive
pocket copy from -proposed to -updates than hammer the buildds every
single time we build bzr.

Mark