Closed
Bug 493773
Opened 14 years ago
Closed 14 years ago
ignore module.ver for version bumps in release automation
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kairo, Assigned: bhearsum)
References
Details
Attachments
(1 file)
1.61 KB,
patch
|
nthomas
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Bug 316387 made module.ver get version automatically from version.txt on both trunk and 1.9.1, so we can make release automation forget any logic for bumping version numbers there.
Assignee | ||
Comment 1•14 years ago
|
||
This has to get done before we spin 3.5rc1 or else the automation will fall down.
Assignee: nobody → bhearsum
Priority: -- → P2
![]() |
Reporter | |
Comment 2•14 years ago
|
||
The immediate thing that should be done is removing module.ver from the bumpFiles in release_master.py We have a comment in buildbotcustom's process/factory.py that cites it, that's an easy fix. Ultimately, in http://hg.mozilla.org/build/tools/file/34afe709615b/release/version-bump.pl#l75 we'll be able to remove all the code that knows how to deal with module.ver. Overall, this is all pretty easy code removal. Do we run into an error right now if we can't replace a version number? I thought we would just not change it and therefore be relatively safe.
Assignee | ||
Comment 3•14 years ago
|
||
(In reply to comment #2) > The immediate thing that should be done is removing module.ver from the > bumpFiles in release_master.py > > We have a comment in buildbotcustom's process/factory.py that cites it, that's > an easy fix. > > Ultimately, in > http://hg.mozilla.org/build/tools/file/34afe709615b/release/version-bump.pl#l75 > we'll be able to remove all the code that knows how to deal with module.ver. > > Overall, this is all pretty easy code removal. Do we run into an error right > now if we can't replace a version number? I thought we would just not change it > and therefore be relatively safe. Yeah, we do hit an error. fwiw, I was just stating it to make sure it gets done - I think it's totally simple & safe enough to do this late.
Assignee | ||
Comment 4•14 years ago
|
||
Pretty self explanatory, I think.
Attachment #378411 -
Flags: review?(nthomas)
Comment 5•14 years ago
|
||
Comment on attachment 378411 [details] [diff] [review] remove module.ver from bumpFiles Missed my automation test :-(
Attachment #378411 -
Flags: review?(nthomas) → review+
Assignee | ||
Comment 6•14 years ago
|
||
Comment on attachment 378411 [details] [diff] [review] remove module.ver from bumpFiles changeset: 1150:d1e83fe8fab1
Attachment #378411 -
Flags: checked‑in+
Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
![]() |
Reporter | |
Comment 7•14 years ago
|
||
Should I file followups for process/factory.py and version-bump.pl changes?
Assignee | ||
Comment 8•14 years ago
|
||
If you don't mind filing a follow-up for version-bump.pl that would be great. I don't want to remove support for it until we do a couple releases with the new module.ver, though. I'll get rid of the comment in factory.py
Updated•10 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•