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)

enhancement

Tracking

(Not tracked)

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.
See Also: → 1358177
Priority: -- → P3
Component: Release Automation: Other → Release Automation: Updates
Severity: normal → S3
QA Contact: rail
Component: Release Automation: Updates → Release Automation
You need to log in before you can comment on or make changes to this bug.