We need to be able to turn these back on if needed, so either saving the revision for backout or commenting out would be good.
(In reply to Aki Sasaki [:aki] from comment #0) > We need to be able to turn these back on if needed, so either saving the > revision for backout or commenting out would be good. for context: per email from akeybl, while he has no more need for v1.0.1 builds, he wants the ability to quickly revive in case of a surprise OMG problem. This is not indefinite. He wants support limited to the 2 most recent releases, so we only need to keep these commented out until after v1.2 ships. Once v1.2 branches (mid Dec2013), the support for v1.2 and v1.1 means no longer supporting v1.0.1 or older.
Since 1.0.1 isn't creating any load (and bug 920624 covers closing that branch) we might as well leave it until December, then remove it completely.
Summary: turn off all builds/tests for b2g18-v1_0_1 → turn off all builds/tests for b2g18-v1_0_1 when we branch for 1.3
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.