Closed
Bug 903357
Opened 12 years ago
Closed 12 years ago
Provide way to ship 24.0b1 updates without having win32 l10n
Categories
(Release Engineering :: Release Automation, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(2 files, 1 obsolete file)
|
1.23 KB,
text/plain
|
rail
:
review+
|
Details |
|
8.71 KB,
patch
|
rail
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
If we can't solve the win32 l10n problem (bug 902091) and don't want to delay shipping any further we need a 'Plan B' to ship updates to 24.0b1. Ideally this will be all locales for mac and linux, en-US only for win32. Once the build problem is resolved we'd go back to providing updates for all locales & platforms.
I've been working on this and will put a proposal up shortly.
| Assignee | ||
Comment 1•12 years ago
|
||
With some fixes to the scripts for bumping update verify configs and snippet generation, we can use a shipped-locales like this. 'linux osx' is appended to every line except en-US, and the ja line loses the win32 reference. If we're OK to land this into mozilla-beta we can also generate updates by forcing the builder rather than manually (ie it works on my laptop).
I've pushed my working up to http://hg.mozilla.org/users/nthomas_mozilla.com/tools/, and here are the configs diffs for
real 24.0b1 build2 - http://people.mozilla.org/~nthomas/b1-configs
a fake 24.0b2 build1 - http://people.mozilla.org/~nthomas/b2-configs
From a quick inspection these are sane, and the snippets to the right things for Windows. I haven't run update verify yet.
| Assignee | ||
Updated•12 years ago
|
Attachment #788078 -
Flags: review?(rail)
| Assignee | ||
Comment 2•12 years ago
|
||
The hunks in this patch are
* when generating snippets, also consider the exceptions in the 'to' build as well as the 'from' build
* when write an update verify config
* skip the line if there are no locales specific
* consider the exceptions in the 'to' build as well as the 'from' build
Attachment #788082 -
Flags: review?(rail)
| Assignee | ||
Comment 3•12 years ago
|
||
Comment on attachment 788082 [details] [diff] [review]
[tools] script changes
There's a glitch with this. The guard on len(locales) < 1 disrupts running update verify on all platforms, but if it's removed at config bump time that also causes issues.
Attachment #788082 -
Attachment is obsolete: true
Attachment #788082 -
Flags: review?(rail)
| Assignee | ||
Comment 4•12 years ago
|
||
Fixed but not pretty. The issues I was having starting win32 update verify are gone and we don't have config lines with locales="" in them.
Attachment #788124 -
Flags: review?(rail)
Updated•12 years ago
|
Attachment #788078 -
Flags: review?(rail) → review+
Comment 5•12 years ago
|
||
Comment on attachment 788124 [details] [diff] [review]
[tools] script changes, v2
lgtm
Attachment #788124 -
Flags: review?(rail) → review+
| Assignee | ||
Comment 6•12 years ago
|
||
Status - I've generated configs and snippets with these two attachments. We get only en-US snippets for windows, all locales otherwise. Spot checks on the snippets look OK, but update verify is going to be the way to flush out any issues. I've tested in staging that update verify still runs, but haven't pushed snippets anywhere so can't say more than that.
I'd suggest deployment looks like this
* land attachment 788078 [details] on mozilla-beta, move tags
* force the updates builder (but you could do this manually via your runme.sh script, just watch out for -b 1 that needs changing to -b 2)
* cross fingers & toes
Comment 7•12 years ago
|
||
Comment on attachment 788124 [details] [diff] [review]
[tools] script changes, v2
https://hg.mozilla.org/build/tools/rev/69b264e3fbe0
Attachment #788124 -
Flags: checked-in+
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
| Assignee | ||
Comment 8•12 years ago
|
||
RESOLVED FIXED depends on how the 24.0b2 updates went, after sorting out any fallout from win32_repack 2 getting run twice.
Assignee: nobody → nthomas
You need to log in
before you can comment on or make changes to this bug.
Description
•