← Back to team overview

fuel-dev team mailing list archive

Re: Launchpad Series and Milestones

 

Alexandra,

This is great. I second Mike, we switch to the new workflow immediately

Thanks,
Roman


On Mon, May 19, 2014 at 6:46 AM, Mike Scherbakov
<mscherbakov@xxxxxxxxxxxx>wrote:

> Alexandra, thanks a lot.
>
> Fuelers, I see no reason to use tag "backports-xxx" anymore to mark a bug
> for possible backport, and I assume that we can switch to new workflow
> immediately. I've verified it, and it seems pretty easy (though UX is much
> to be desired, but once you know where to click...).
>
> Regards,
>
>
> On Mon, May 19, 2014 at 3:23 PM, Aleksandra Fedorova <
> afedorova@xxxxxxxxxxxx> wrote:
>
>> Hi, everyone,
>>
>> we have updated our series structure at Launchpad. Please, take a look
>> at https://launchpad.net/fuel/+series
>>
>> Each series represents one Fuel release line (4.1.x, 5.0.x, 5.1.x,...).
>> Each release, for example 4.1.x, has several milestones: initial release
>> milestone (4.1) and consequent bugfixes milestones (4.1.1, 4.1.2,...).
>>
>> By default all the bugs are considered to be in the current "focus of
>> development" series, which is now set to 5.0.x. See "Development focus"
>> field at https://launchpad.net/fuel
>>
>> If you think that bug affects another release, you should click
>> "nominate for series" (or, if you have extended rights, "target for
>> series") link on the bug page and mark the release, affected by the bug.
>> This will create new row in bug description, where you can choose
>> another milestone, status, assignee and so on for the same bug but in
>> this particular series.
>>
>> Currently everyone in Fuel Bugs group (and, therefore, Fuel Core group)
>> is able to target issue to series 4.1.x, 5.0.x and 5.1.x.
>>
>> Note that the fact that certain release affected by the bug doesn't
>> necessarily mean that the bug should and will be fixed in its series.
>>
>> For example, if bug 12345 affects both releases 4.1 and 5.0, but we
>> don't plan to fix it in 4.1, then we target the bug in both 4.1.x and
>> 5.0.x series and change the status in the 4.1.x series row to "Won't
>> fix".
>>
>> Please use this page for future references and updates:
>> https://wiki.openstack.org/wiki/Fuel/Launchpad_Series
>>
>> --
>> Aleksandra Fedorova
>> bookwar
>>
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Mike Scherbakov
> #mihgen
>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>

References