Open Bug 1269547 Opened 8 years ago Updated 6 years ago

"milestone" for changesets close to branch merges is wrong

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Product:
Developer Services
Component:
Mercurial: hg.mozilla.org
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: glandium, Unassigned)

Details

After branch merges (e.g. central -> aurora), the version is bumped: on aurora, n.0a1 becomes n.0a2, on central, it becomes n+1.0a1.

Changesets after the version bump are correctly identified with their milestone, but anything that has landed on integration branches and wasn't merged to central by the time the merge happened are misidentified to the previous milestone.

Technically, something similar happens on aurora for changesets between the last released aurora snapshot and the merge. Likewise on beta for changesets between the last released beta and the merge.

I wrote on irc that a more accurate thing would be "what is the last FIREFOX_n_AURORA_BASE" tag that is an ancestor of that changeset?" but even that is not the whole story.
QA Contact: hwine → klibby
You need to log in before you can comment on or make changes to this bug.