[devops] Script is needed which targets dev milestone every X hours if stable is targeted

[Mike Scherbakov]

Example:
QA engineer finds a bug in 5.0.1 (5.0.x series), which is milestone for stable/5.0 branch, and current development (master) is 5.1 milestone (5.1.x series).
According to our latest Fuel discussions, we need to automate auto-proposal for development milestone (5.1) to avoid possible loss of bugs in development version, while it is going to be fixed in stable branch.

To generalize it even more, I request to make such a script which will be "affecting" (in terms of LP) development milestone for any new bug, which would be created and targeting milestone which is older than development (for example, 4.1.2, 5.0.1 should affect 5.1).

There is no need to check all bugs in the past, and I assume that script will have such a logic that it will start doing this only for new bugs, starting from the moment of script run.

Then for developers / bug team, if bug doesn't really affect development milestone and affects only what it was proposed for, then it should be marked as "Invalid" or "Won't fix" for development milestone, with corresponding comment in the LP bug.

Original purpose of this script was extended to also go over all Critical bugs in current development milestone and target maintenance milestone. Like if you have 6.1 Critical, it will target 6.0.1. Also, it does the same thing for all customer-found tagged bugs. It's being discussed with sustaining team if we want to target all ".*-updates" milestones of such 6.1 Critical & customer-found.

[Igor Shishkin (teran)]

Dmitry, as I remember you had write some launchpad scripts. What they able to do?

Thanks.

[Igor Shishkin (teran)]

ETA: after 6.0 release.

[Mike Scherbakov (mihgen)]

This is not Medium, Igor. This was not Critical just because it does not block release and current work. Though we always have pain, and we have to slip releases just because we do not have this script running.
It is not acceptable to spend 4 months looking at High priority bug, and then move to Medium just because.

Such things as https://bugs.launchpad.net/mos/+bug/1375245, https://bugs.launchpad.net/fuel/+bug/1401152 would not happen if we have this script.

[Andrey Nikitin (heos)]

Mike, what script should do when a new bug has not a milestone?

[Mike Scherbakov (mihgen)]

Target "current focus development milestone". There is such a term in
launchpad.
On Dec 25, 2014 7:30 PM, "Andrey Nikitin" <email address hidden> wrote:

> Mike, what script should do when a new bug has not a milestone?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1349380
>
> Title:
> [devops] Script is needed which targets dev milestone every X hours if
> stable is targeted
>
> Status in Fuel: OpenStack installer that works:
> In Progress
>
> Bug description:
> Example:
> QA engineer finds a bug in 5.0.1 (5.0.x series), which is milestone for
> stable/5.0 branch, and current development (master) is 5.1 milestone (5.1.x
> series).
> According to our latest Fuel discussions, we need to automate
> auto-proposal for development milestone (5.1) to avoid possible loss of
> bugs in development version, while it is going to be fixed in stable branch.
>
> To generalize it even more, I request to make such a script which will
> be "affecting" (in terms of LP) development milestone for any new bug,
> which would be created and targeting milestone which is older than
> development (for example, 4.1.2, 5.0.1 should affect 5.1).
>
> There is no need to check all bugs in the past, and I assume that
> script will have such a logic that it will start doing this only for
> new bugs, starting from the moment of script run.
>
> Then for developers / bug team, if bug doesn't really affect
> development milestone and affects only what it was proposed for, then
> it should be marked as "Invalid" or "Won't fix" for development
> milestone, with corresponding comment in the LP bug.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1349380/+subscriptions
>

[Andrey Nikitin (heos)]

Quote: "it will start doing this only for new bugs, starting from the moment of script run."

I think we can use creation date of "current focus development milestone".

For 6.1.x is - 13.10.2014 (https://api.launchpad.net/1.0/fuel/6.1.x/)

Is it correct?

[Mike Scherbakov (mihgen)]

Fine with me

[Andrey Nikitin (heos)]

Created a draft of request: https://review.fuel-infra.org/#/c/2323/.

[Andrey Nikitin (heos)]

Created request https://review.fuel-infra.org/#/c/2502/.

[Andrey Nikitin (heos)]

Work in progress by comments from Mike.

[Andrey Nikitin (heos)]

Script was updated and commited to https://review.fuel-infra.org/#/admin/projects/fuel-infra-packages/python-lpbugmanage repository.

[Mike Scherbakov (mihgen)]

Code is under development here: https://github.com/mihgen/lp-assigner