[OpenStack-docs] When to change a bug from fix-committed to fix-released?

Tom Fifield tom at openstack.org
Fri Apr 24 00:07:23 UTC 2015



On 24/04/15 10:03, Jeremy Stanley wrote:
> On 2015-04-24 09:54:47 +1000 (+1000), Tom Fifield wrote:
> [...]
>> You could argue that a bug fixed in a guide-in-progress that is
>> not yet published (eg networking?) should set status to
>> Fix-committed until the entire guide is published ... but does
>> anyone really want to go and change the status of a ton of bugs
>> when that happens? :)
> [...]
>
> I'm certainly not arguing in favor of extra process, but _if_ you
> decide you need it Thierry does have a script to handle that part.
>
> <URL: https://git.openstack.org/cgit/openstack-infra/release-tools/tree/process_bugs.py >
>
> However it also depends on you creating series milestones and
> targeting the bugs you're planning to handle that way.
>

Indeed :)

For reference - at the moment, we have just one milestone per release, eg

https://launchpad.net/openstack-manuals/+milestone/kilo



More information about the OpenStack-docs mailing list