Closed
Bug 406627
Opened 17 years ago
Closed 17 years ago
adjust Bootstrap to use patcher configs in mozilla/tools/patcher-configs
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
Details
Attachments
(1 file)
3.07 KB,
patch
|
rhelmer
:
review+
|
Details | Diff | Splinter Review |
Now that the configs are in public CVS, Bootstrap should be pulling them from it.
Assignee | ||
Updated•17 years ago
|
Assignee: nobody → bhearsum
Priority: -- → P2
Assignee | ||
Comment 1•17 years ago
|
||
I haven't done a run with this code since it's pretty simple. Unit tests pass, though.
Attachment #293675 -
Flags: review?(rhelmer)
Comment 2•17 years ago
|
||
Comment on attachment 293675 [details] [diff] [review]
use public versions of patcher configs
Looks good.
Just a reminder, we'll need to resync the patcher configs, as this code modifies them in CVS so it must have drifted by now. I guess we should do that after the current round of releases (fx 3.0b2, tb 15014) are done.
Attachment #293675 -
Flags: review?(rhelmer) → review+
Assignee | ||
Comment 3•17 years ago
|
||
Checking in Bootstrap/Step/PatcherConfig.pm;
/cvsroot/mozilla/tools/release/Bootstrap/Step/PatcherConfig.pm,v <-- PatcherConfig.pm
new revision: 1.11; previous revision: 1.10
done
Checking in Bootstrap/Step/Updates.pm;
/cvsroot/mozilla/tools/release/Bootstrap/Step/Updates.pm,v <-- Updates.pm
new revision: 1.29; previous revision: 1.28
done
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•