Closed
Bug 659221
Opened 13 years ago
Closed 13 years ago
Add tags to comm-central, comm-aurora, and comm-beta for branch points.
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
References
Details
With our setting up of comm-central/comm-aurora/comm-beta it would be good to have tags on all 3 of our branch points. I'm not particular on our tag names (I suggest COMM_AURORA_<date> and COMM_BETA_<date>) but the tagging cset should be the same (pushed to multi repos) I'm not doing this myself as I don't know where we stand on comm-beta atm (if we are already considered as branched). Nor will I be around at 10A PDT.
Comment 1•13 years ago
|
||
Well the aurora and beta points shouldn't actually need tagging, as I was hoping they wouldn't have diverged and just been straight clones and we could have branched just by tagging latest, however it appears they had an extra cset pushed :-( I'll be sorting this out later. If anything it'll be good practice for next time around.
Assignee: nobody → mbanner
Comment 2•13 years ago
|
||
Comm-central and comm-aurora are done. Thunderbird isn't using comm-beta yet, so I'm not touching that...
Assignee: mbanner → bugspam.Callek
Assignee | ||
Comment 3•13 years ago
|
||
Both aurora and beta repos tagged for diverging point: http://hg.mozilla.org/releases/comm-beta/rev/330096d71695 in separate pushes: http://hg.mozilla.org/releases/comm-aurora/rev/691cb5645564 http://hg.mozilla.org/releases/comm-beta/rev/c79db400bb91
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•