Closed
Bug 463284
Opened 16 years ago
Closed 16 years ago
Tracking bug for Build and Release of TB2.0.0.18
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
Details
Attachments
(2 files, 1 obsolete file)
1.20 KB,
patch
|
nthomas
:
review+
|
Details | Diff | Splinter Review |
3.05 KB,
patch
|
coop
:
review+
|
Details | Diff | Splinter Review |
Still waiting on one change on the relbranch.
Assignee | ||
Comment 1•16 years ago
|
||
The usual version bumps and so on. I've left xx:xx for the HH:MM of the pullDates out at the moment, since that's still unknown. Planning to fill them in on checkin just for completeness, since they're not used when we define a relbranch override. I also left the update packaging tag at _R4 to match Fx2.0.0.18, we should update those for the next release for sure.
Attachment #346527 -
Flags: review?(bhearsum)
Comment 2•16 years ago
|
||
Comment on attachment 346527 [details] [diff] [review] Update bootstrap config for Tb20018 build1 Looks fine. Also, r=bhearsum on checking in the proper times when you get them.
Attachment #346527 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 3•16 years ago
|
||
Checking in tb-moz18-bootstrap.cfg; /cvsroot/mozilla/tools/release/configs/tb-moz18-bootstrap.cfg,v <-- tb-moz18-bootstrap.cfg new revision: 1.29; previous revision: 1.28 done and moved RELEASE_AUTOMATION_M11 onto rev 1.29.
Attachment #346527 -
Attachment is obsolete: true
Attachment #346584 -
Flags: review+
Assignee | ||
Comment 4•16 years ago
|
||
Attachment #346651 -
Flags: review?(ccooper)
Updated•16 years ago
|
Attachment #346651 -
Flags: review?(ccooper) → review+
Assignee | ||
Updated•16 years ago
|
Attachment #346651 -
Attachment description: Bump version to 2.0.0.19pre → [checked in] Bump version to 2.0.0.19pre
Assignee | ||
Updated•16 years ago
|
Priority: -- → P2
Assignee | ||
Comment 5•16 years ago
|
||
Shipped.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•