Closed
Bug 730856
Opened 12 years ago
Closed 12 years ago
Tracking bug for build and release of Firefox 10.0.3 ESR
Categories
(Release Engineering :: Release Requests, defect)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
References
Details
(Whiteboard: [releases])
Attachments
(4 files, 2 obsolete files)
9.40 KB,
patch
|
mozilla
:
review+
|
Details | Diff | Splinter Review |
881 bytes,
patch
|
rail
:
review+
|
Details | Diff | Splinter Review |
1.83 KB,
patch
|
rail
:
review+
|
Details | Diff | Splinter Review |
1.80 KB,
patch
|
rail
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
Waiting for 'go'.
Assignee | ||
Comment 1•12 years ago
|
||
Evidently I only created the staging_release-fennec-mozilla-esr10.py in bug 727580 .
Attachment #601090 -
Flags: review?(bhearsum)
Comment 2•12 years ago
|
||
Comment on attachment 601090 [details] [diff] [review] 10.0.3esr configs Review of attachment 601090 [details] [diff] [review]: ----------------------------------------------------------------- ::: mozilla/release-fennec-mozilla-release.py @@ +32,5 @@ > releaseConfig['sourceRepositories'] = { > 'mobile': { > + 'name': 'mozilla-esr10', > + 'path': 'releases/mozilla-esr10', > + 'revision': 'TBD', super tiny nit: it's good to drop the quotes for TBD. Doing so causes a syntax error, so you can't accidentally try to tag something called 'TBD' if you land the patch accidentally.
Attachment #601090 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 3•12 years ago
|
||
(In reply to Ben Hearsum [:bhearsum] from comment #2) > super tiny nit: it's good to drop the quotes for TBD. Doing so causes a > syntax error, so you can't accidentally try to tag something called 'TBD' if > you land the patch accidentally. Yeah. I put it in quotes to run test-masters for the new file, then didn't remove them. Can do in the future.
Comment 4•12 years ago
|
||
Comment on attachment 601090 [details] [diff] [review] 10.0.3esr configs Al just pointed out to me that the nightly build versions are confusing, because they're using an old version number (eg, right now they're called "10.0.2"). Can you bump the nextAppVersion and nextMilestone to 10.0.4esr or 10.0.4esrpre when you land?
Assignee | ||
Comment 5•12 years ago
|
||
Attachment #601090 -
Attachment is obsolete: true
Attachment #601413 -
Flags: review?(bhearsum)
Updated•12 years ago
|
Attachment #601413 -
Flags: review?(bhearsum) → review+
Comment 6•12 years ago
|
||
Aki, Please consider to enable signing on demand for Firefox since all needed patches backported to mozilla-esr10 (bug 731378). This require 3 changes: 1) bump releaseConfig['patcherToolsTag'] to 'UPDATE_PACKAGING_R16' 2) remove releaseConfig['enableSigningAtBuildTime'] = False 3) releaseConfig['enablePartialMarsAtBuildTime'] = False A patch attached (including yours). Staging release passed fine.
Assignee | ||
Updated•12 years ago
|
Attachment #601942 -
Flags: review+
Assignee | ||
Updated•12 years ago
|
Attachment #601413 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Component: Release Engineering → Release Engineering: Releases
QA Contact: release → bhearsum
Assignee | ||
Comment 8•12 years ago
|
||
Attachment #602509 -
Flags: review?(lsblakk)
Updated•12 years ago
|
Attachment #602509 -
Flags: review?(lsblakk) → review+
Assignee | ||
Comment 9•12 years ago
|
||
Attachment #603329 -
Flags: review?(rail)
Updated•12 years ago
|
Attachment #603329 -
Flags: review?(rail) → review+
Assignee | ||
Comment 10•12 years ago
|
||
Attachment #604482 -
Flags: review?(rail)
Updated•12 years ago
|
Attachment #604482 -
Flags: review?(rail) → review+
Assignee | ||
Comment 11•12 years ago
|
||
Comment on attachment 604482 [details] [diff] [review] move esr10 to bm08 http://hg.mozilla.org/build/tools/rev/abe42df2d7c9
Attachment #604482 -
Flags: checked-in+
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 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
•