Closed Bug 644429 Opened 14 years ago Closed 14 years ago

Add GECKO_2_0_BASE tag to m-c/m-2.1/m-2.0 and GECKO_2_1_BASE tag to m-c/m-2.1

Categories

(Release Engineering :: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sgautherie, Assigned: bhearsum)

References

Details

It looks like m-2.0 (and m-2.1, though I've barely discovered its existence) were branched without tagging their m-c base. Unlike existing GECKO_1_9_1_BASE and GECKO_1_9_2_BASE tags. GECKO_2_0_BASE should be added to all affected repositories, after the fact now :-| The relevant changeset is e56ecd8b3a68. Fwiw, its previous changeset is 290712e55ade which was tagged THUNDERBIRD_3_3a3_RELEASE (in m-c). Ftr, see http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/c04d9913c35834f2/644ccb63c0635f57 NB: And branching steps should be checked to include this tagging _before_ branching... ***** I guess a GECKO_2_1_BASE tag should also be added to m-c/m-2.1, if someone can detail m-2.1 status. Otherwise, I'll file a separate bug.
(In reply to comment #0) > Fwiw, its previous changeset is 290712e55ade which was tagged > THUNDERBIRD_3_3a3_RELEASE (in m-c). Mark, while there, THUNDERBIRD_3_3a3_BUILD1 and THUNDERBIRD_3_3a3_RELEASE are in m-c/m-2.1, but "missing" in m-2.0. (probably because m-2.0 branched in the meantime...)
Blocks: 566679
Blocks: 639972
Summary: Add GECKO_2_0_BASE tag to m-c/m-2.1/m-2.0 → Add GECKO_2_0_BASE tag to m-c/m-2.1/m-2.0 and GECKO_2_1_BASE tag to m-c/m-2.1
(In reply to comment #1) > (In reply to comment #0) > > Fwiw, its previous changeset is 290712e55ade which was tagged > > THUNDERBIRD_3_3a3_RELEASE (in m-c). > > Mark, while there, THUNDERBIRD_3_3a3_BUILD1 and THUNDERBIRD_3_3a3_RELEASE are > in m-c/m-2.1, but "missing" in m-2.0. > (probably because m-2.0 branched in the meantime...) I don't really care. It was released from m-c not from m-2.0, and as far as I'm concerned, that's the important bit.
Assignee: nobody → bhearsum
I pushed all of these a few minutes ago.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
(In reply to comment #3) > I don't really care. It was released from m-c not from m-2.0, and as far as I'm > concerned, that's the important bit. Sure. Yet, do you agree that I manually tag it in m-2.0 ftr? (In reply to comment #4) > I pushed all of these a few minutes ago. Almost: GECKO_2_0_BASE is still missing in m-2.1.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.