Open
Bug 1361877
Opened 8 years ago
Updated 6 months ago
improve partial update logic for new locales
Categories
(Release Engineering :: Release Automation, enhancement, P3)
Release Engineering
Release Automation
Tracking
(Not tracked)
NEW
People
(Reporter: mozilla, Unassigned)
References
Details
Aiui, right now:
- we generate complete mars for builds and repacks
- we generate partial mars for locales that aren't new
- we submit all mars to balrog
The second point is a problem for locales that were new one or two betas ago. Because there isn't a build to generate partials from on the previous release, partial mar generation fails, and we don't submit any mars to balrog.
If we're able to check the locales for a given previous release, we can determine whether we should expect a partial mar between the two releases.
Updated•8 years ago
|
Priority: -- → P3
Updated•7 years ago
|
Component: Release Automation: Other → Release Automation: Updates
Updated•2 years ago
|
Severity: normal → S3
Updated•6 months ago
|
QA Contact: rail
Updated•6 months ago
|
Component: Release Automation: Updates → Release Automation
You need to log in
before you can comment on or make changes to this bug.
Description
•