Closed
Bug 492549
Opened 15 years ago
Closed 15 years ago
Do XULRunner 1.9.0.10 release
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mossop, Assigned: mossop)
Details
Attachments
(1 file)
1.39 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #483236 +++ Make a XULRunner release to match the Firefox 3.0.10 release
Assignee | ||
Comment 1•15 years ago
|
||
Patches the xulrunner config to match Firefox 3.0.10
Attachment #376931 -
Flags: review?(bhearsum)
Updated•15 years ago
|
Attachment #376931 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 2•15 years ago
|
||
Landed and tagged: Checking in xr-moz19-bootstrap.cfg; /cvsroot/mozilla/tools/release/configs/xr-moz19-bootstrap.cfg,v <-- xr-moz19-bootstrap.cfg new revision: 1.15; previous revision: 1.14 done lambda:configs dave$ cvs tag -F RELEASE_AUTOMATION_M13 xr-moz19-bootstrap.cfg T xr-moz19-bootstrap.cfg
Assignee | ||
Comment 3•15 years ago
|
||
Candidate builds are now available at ftp://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/1.9.0.10-candidates/build1/
Comment 4•15 years ago
|
||
Are we ready to release this, now that 1.9.0.11 is underway ?
Comment 5•15 years ago
|
||
Looks ok to me
Comment 6•15 years ago
|
||
Ok, I'll push it onto the mirrors.
Comment 7•15 years ago
|
||
Pushed to the mirrors and available from http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.0.10/ in an hour or so. These will need an update once the mirrors are OK https://developer.mozilla.org/En/XULRunner_1.9_Release_Notes https://developer.mozilla.org/En/Gecko_SDK
Comment 8•15 years ago
|
||
This is now shipped. Anything left to do here, or is this FIXED?
Assignee | ||
Comment 9•15 years ago
|
||
Updated the pages on MDC, I think we're done here.
Status: NEW → RESOLVED
Closed: 15 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
•