1459734 - Update milestones and versions

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Dylan Hardison [:dylan] (he/him)]

This has been part of the release-tracking flags process recently, but this time it's a separate bug. I hope it is fully automated before next time.

Comment 1

[Dylan Hardison [:dylan] (he/him)]

Attachment: Milestones Added.txt

Comment 2

[Dylan Hardison [:dylan] (he/him)]

Attachment: Versions Added

Comment 3

[Dylan Hardison [:dylan] (he/him)]

When you've a moment, check if I've missed any products?

Also, we still have yet to firmally establish which milestones should be disabled. it's all over the place depending on the product.

Comment 4

[Raul Gurzau (:RaulG)]

Milestone weren't up to date when merging. :RyanVM|afk

Comment 5

[Dylan Hardison [:dylan] (he/him)]

(In reply to Raul Gurzau (:RaulGurzau) from comment #4)
> Milestone weren't up to date when merging. :RyanVM|afk

In which product?

Comment 6

[Raul Gurzau (:RaulG)]

This is the merge: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=59005ba3cd3e7b3f9e8804bea881bf4c3a755d7

The products are firefox, toolkit, core mostly.

Comment 7

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

They were there, but bugherder didn't use the firefox 62 milestone but the 61 one. It worked correctly for mozilla62. IIRC, that depends on the sort order of the milestones.

Comment 8

[Dylan Hardison [:dylan] (he/him)]

(In reply to Sebastian Hengst [:aryx][:archaeopteryx] (needinfo on intermittent or backout) from comment #7)
> They were there, but bugherder didn't use the firefox 62 milestone but the
> 61 one. It worked correctly for mozilla62. IIRC, that depends on the sort
> order of the milestones.

Okay. I'll have to review the sort order of every milestone in every product... anyway you could help me narrow that down?

Comment 9

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

What external tools break if we made all firefox-related products use a consistent milestone and version scheme?

Comment 10

[Ryan VanderMeulen [:RyanVM]]

I don't understand the question, nor could I possibly know every tool that uses the API and depends on this information. I know that Bugherder assumes things are in a consistent order, which is why issues were hit here.

Comment 11

[Dylan Hardison [:dylan] (he/him)]

As I said in IRC, I think that was just a timing issue. Next ieration the marker will be moved at the same time as the new version is added.

I reviewed every product and the markers are good now.

Comment 12

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Thank you. Bug 1460013 will make bugherder more robust.

The old assumption was that the first milestone after "---" is the right one for most products: https://github.com/mozilla/bugherder/blob/master/bugherder/js/ConfigurationData.js#L8

In the future it will always look for a direct match for the milestone.