[Openstack-stable-maint] Preparing for 2013.1.1 stable/grizzly WAS Proposed stable/grizzly release dates

Alan Pevec apevec at gmail.com
Wed Apr 24 21:23:51 UTC 2013


Hi Adam,

> -  The LP search you linked to only contains bugs with open tasks. Adding
> 'Fix Committed' [1] shows many more that are tagged, fixed in project's
> master but not proposed to stable/grizzly.  I assume we should also make
> sure these get tracked as well?

Yes, part of the stable release process[1] to identify all bugs with
patches committed to the stable branch and target them to Grizzly
series in Launchpad.

>  I see a few relatively small patches that seem suitable for stable backport, eg [2]

Yep, that one certainly is a good stable candidate.

> -  Should core-devs/PTLs be nominating bugs as affecting Grizzly before
> someone else proposes a backport?  Or are we only looking for tags?

As others replied, both tags and target series are useful when
preparing backports, but eventually tags are stripped and all fixed
bugs must target series and milestone, so that they show up on the
milestone Launchpad page.

Cheers,
Alan

[1] https://wiki.openstack.org/wiki/StableBranchRelease



More information about the Openstack-stable-maint mailing list