Closed
Bug 577875
Opened 14 years ago
Closed 14 years ago
For Mozilla 2, gecko version numbers will be 2.0.x, not 2.0.0.x
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: benjamin, Unassigned)
Details
joduinn asked me to file a bug to remind you guys that for Mozilla 2, the minor updates platform version number will be 2.0.x, not 2.0.0.x. This may require reconfiguring the version-bump/tagging code.
Comment 1•14 years ago
|
||
Starting with tips of m-c and build/tools, here's what we'll be doing if the config sets milestone=2.0.1, version=4.0.1 perl tools/release/version-bump.pl -w mozilla-central -t FIREFOX_4_0_1_RELEASE -a browser -v 4.0.1 -m 2.0.1 config/milestone.txt js/src/config/milestone.txt browser/config/version.txt diff --git a/browser/config/version.txt b/browser/config/version.txt --- a/browser/config/version.txt +++ b/browser/config/version.txt @@ -1,1 +1,1 @@ -4.0b2pre +4.0.1 diff --git a/config/milestone.txt b/config/milestone.txt --- a/config/milestone.txt +++ b/config/milestone.txt @@ -10,4 +10,4 @@ # hardcoded milestones in the tree from these two files. #-------------------------------------------------------- -2.0b2pre +2.0.1 diff --git a/js/src/config/milestone.txt b/js/src/config/milestone.txt --- a/js/src/config/milestone.txt +++ b/js/src/config/milestone.txt @@ -10,4 +10,4 @@ # hardcoded milestones in the tree from these two files. #-------------------------------------------------------- -2.0b2pre +2.0.1 No error, sane diff. Added a comment to the release config to help us remember: http://hg.mozilla.org/build/buildbot-configs/rev/3967796fe6b1
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Assignee | ||
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
•