MicroReleaseException for Banshee SRUs

[Mark Shuttleworth]

On 02/06/11 14:36, Chow Loong Jin wrote:
> At this point, a git branch, named stable-x.y will be created from the tag for
> the new stable series. Development and bug fixes will continue as usual in the
> master branch, and bugfixes deemed important and stable enough will be
> cherry-picked into the stable-x.y branch. At unspecified intervals (usually
> based on the number/importance of the bugfixes), a new stable release will be
> made, from this branch, such as the recent 2.0.1 version.

Chow Loong, is there a documented policy for "important and stable"? In
general, we like to grant these kinds of micro-release exceptions to
empower upstreams, but we do so only when there's consensus between us
and upstream on the criteria for such changes in a stable release.

It sounds like you are adopting a great practice I'd simply like to
confirm that we're on the same page as to the nature of such changes. If
you could point the TB to a document describing the criteria and stable
change review / approval process, as well as list the changes made in
2.0 -> 2.0.1 as an example, that would be most helpful.

Separately, if your community does not already have a packageset and
more direct upload permissions, it might be worth setting out to achieve
that too, so you can have even more control of the flow of your code
into the archives.

Mark