Milestones need updating to series

Bug #40978 reported by Mark Shuttleworth on 2006-04-23
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

There is now a milestone admin page which allows us to select the
relevant ProductSeries or DistroRelease for a milestone. Some milestones
have been automatically assigned to a series/release but the balance
(about 50) need to be done manually. This is because, where there is
more or less than one series for the milestone product/distro, we could
not guess automatically which series to use. In these cases:

 1. we need to create a series if there is not already an appropriate
one for that milestone
 2. in the case of distributions, with the exception of Ubuntu and Sid
there should not be any distroreleases or milestones
 3. we need to assign all milestones to a series or distrorelease

New milestones can only be created on a series or distrorelease, so its
just a question of updating all the old ones, then we can enforce the
existence of a series or distrorelease at the database level.

The following query will give you the list of milestones that need this

 SELECT,, FROM Milestone
Distribution ON ORDER BY, WHERE Milestone.productseries IS NULL
AND Milestone.distrorelease IS NULL;

 affects /products/launchpad

 assignee <email address hidden>

Changed in launchpad:
assignee: nobody → kiko
Christian Reis (kiko) wrote :

This is mostly done. The items that remain to be fixed are:
 - One milestone attached to exdoap, which is a hidden product.
 - Two milestones attached to baltix, which doesn't have a distribution release yet.

Changed in launchpad:
status: Unconfirmed → Confirmed
Christian Reis (kiko) on 2006-07-12
Changed in launchpad:
status: Confirmed → In Progress
Christian Reis (kiko) wrote :

This is now actively blocked on bug #58250, and I won't be able to go into that in the near future.

Changed in launchpad:
assignee: kiko → nobody
Changed in launchpad:
status: In Progress → Confirmed
Mantas Kriaučiūnas (mantas) wrote :

Christian Reis wrote on 2006-06-27:
> This is mostly done. The items that remain to be fixed are:
> - Two milestones attached to baltix, which doesn't have a distribution release yet.

I'm Baltix distro administrator and I will be happy if I will have a permission to add new releases (series) in Baltix distribution see bug #211223 for more info.
Maybe someone from Launchpad admins can register at least 6 main Baltix releases (1.x, 2.0, 2.7, 3.0, 3.1 and 3.5) until that bug is fixed?

Curtis Hovey (sinzui) wrote :

This problem appears to have grown. Bug 401157 is ultimately cause by data being in a bad state.

We need a new report to understand the scope of the problem. We have given users the power to fix their milestone series, but we may be able to fix them with a query.

affects: launchpad-foundations → launchpad-registry
Changed in launchpad-registry:
assignee: nobody → Curtis Hovey (sinzui)
importance: Medium → High
milestone: none → 2.2.7
Curtis Hovey (sinzui) on 2009-07-20
tags: added: story-series-milestones-releases
Curtis Hovey (sinzui) wrote :

I had the power to fix all but but two of the milestones. Baltix has the last two bad milestones that need series. Question 77453 was already created asking an admin to create some series so we are very close to completing the work.

Changed in launchpad-registry:
status: Triaged → In Progress
Curtis Hovey (sinzui) on 2009-07-30
Changed in launchpad-registry:
milestone: 2.2.7 → 2.2.8
Curtis Hovey (sinzui) wrote :

The Baltix drivers have the power to create the series missing series and can assign them to the two broken milestones.

Changed in launchpad-registry:
milestone: 2.2.8 → 3.0
Curtis Hovey (sinzui) on 2009-09-25
Changed in launchpad-registry:
milestone: 3.0 → 3.1.10
Curtis Hovey (sinzui) wrote :

All hail Chex. He assigned the last two milestones to a series.

Changed in launchpad-registry:
status: In Progress → Fix Released
Curtis Hovey (sinzui) on 2009-10-09
tags: added: tech-debt
Curtis Hovey (sinzui) on 2017-05-15
Changed in launchpad:
assignee: Curtis Hovey (sinzui) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers