Closed
Bug 499594
Opened 16 years ago
Closed 16 years ago
Release updates tools (patcher, config bumps) need a brand option
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kairo, Assigned: kairo)
References
Details
Attachments
(3 files)
|
14.59 KB,
patch
|
bhearsum
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
|
1.84 KB,
patch
|
bhearsum
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
|
8.53 KB,
patch
|
Details | Diff | Splinter Review |
In bug 498110 work toward SeaMonkey release automation (bug 493451), I came realize that we assume the capitalized brand name to be a first-letter-uppercased version of the lowercase app name. In the case of "seamonkey"->"SeaMonkey" that method doesn't work, so we need to make all tools that rely on that aware of a brand name options where we can pass this separately (and fall back to the previous behavior if it's omitted).
This affects patcher-config-bump.pl, update-verify-bump.pl and even patcher2.pl.
| Assignee | ||
Comment 1•16 years ago
|
||
This is the patch for the bump scripts against build/tools on hg, falling back to the previous behavior nicely.
One part if this patch is slightly unrelated but I hope I can sneak it in with this instead of doing an extra patch against patcher-config-bump.pl - we have different release notes URLs for SeaMonkey.
Attachment #384316 -
Flags: review?(bhearsum)
| Assignee | ||
Comment 2•16 years ago
|
||
Thankfully, the patcher patch is quite easy, as it's already abstracting getting this name with the GetApp() function.
Attachment #384318 -
Flags: review?(bhearsum)
Comment 3•16 years ago
|
||
I did a mock release with this patch today and it went great. I'll do an actual review tomorrow.
Updated•16 years ago
|
Attachment #384316 -
Flags: review?(bhearsum) → review+
Comment 4•16 years ago
|
||
Comment on attachment 384316 [details] [diff] [review]
bump scripts patch, v1
This is fine. There's a bit of context bitrot, so please be careful when you land it.
Comment 5•16 years ago
|
||
Comment on attachment 384318 [details] [diff] [review]
patcher patch, v1
Yeah, seems fine.
Attachment #384318 -
Flags: review?(bhearsum) → review+
Comment 6•16 years ago
|
||
Comment on attachment 384318 [details] [diff] [review]
patcher patch, v1
Checking in MozAUSConfig.pm;
/cvsroot/mozilla/tools/patcher/MozAUSConfig.pm,v <-- MozAUSConfig.pm
new revision: 1.19; previous revision: 1.18
done
Attachment #384318 -
Flags: checked‑in+
Comment 7•16 years ago
|
||
Comment on attachment 384316 [details] [diff] [review]
bump scripts patch, v1
changeset: 315:50e628530fff
Attachment #384316 -
Flags: checked‑in+
Comment 8•16 years ago
|
||
I created UPDATE_PACKAGING_R9 in the tools repository and CVS (by following the instructions here: https://bugzilla.mozilla.org/show_bug.cgi?id=420947#c17).
As expected, the only differences between R8 and R9 in CVS are the patch in this bug, some Bootstrap config files, and the tags in client.mk. I'm attaching a diff in case anyone wants to verify.
| Assignee | ||
Comment 9•16 years ago
|
||
Thanks for checking in, marking fixed as the patches seem to stick.
Status: ASSIGNED → RESOLVED
Closed: 16 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
•