Closed
Bug 847603
Opened 11 years ago
Closed 11 years ago
default the l10n dashboard check to False
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
(Whiteboard: [shipit])
This check hasn't caught a real error in a long time, but it's often caused headaches when trying to start releases because we've forgotten to disable it. Is it worth the trouble?
Assignee | ||
Comment 1•11 years ago
|
||
Rail and I just talked about this and realized that most of our pain around this check is because it defaults to on, which causes problems for all final releases and esrs. I pushed a change to invert that. This, along with bug 847424 should make the check less painful without disabling it completely. http://git.mozilla.org/?p=build/release-kickoff.git;a=commitdiff;h=7467f6d416c3174c0fc76886a790bdf187ded715 Still need to get this change deployed to production.
Assignee: nobody → bhearsum
Summary: consider ripping out l10n dashboard check from ship it / release sanity → default the l10n dashboard check to False
Assignee | ||
Comment 2•11 years ago
|
||
in production.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•