We're shipping mn and tr as Beta for 3.5, and we decided to not include those two locales in the list of manual major update requests. Getting a bug on file that we get done whatever it takes to do that.
We can do this, no big deal, but I'm curious what the reason is.
The reason is that we have green builds for both, but both teams have been mostly offline since B4, so there wasn't any path for feedback on the Betas making it into the builds we're shipping. So we're keeping them in Beta to continue to gather feedback based on the best gecko code we have. They also lack a bunch of webpages that are part of our non-beta official releases.
We won't actually be generating snippets with this config, since we now have to null out the already-pushed mn and try test snippets, but we should modify the patcher config for completeness. See https://wiki.mozilla.org/Releases/Firefox_3.5/BuildNotes for details on the fixup
Attachment #385380 - Flags: review?(nthomas)
Assignee: nobody → bhearsum
Priority: -- → P2
Flags: blocking1.9.1? → blocking1.9.1+
Attachment #385380 - Flags: review?(nthomas) → review+
Comment on attachment 385380 [details] [diff] [review] remove mn and tr from MU patcher config Checking in moz19-branch-major-update-patcher2.cfg; /cvsroot/mozilla/tools/patcher-configs/moz19-branch-major-update-patcher2.cfg,v <-- moz19-branch-major-update-patcher2.cfg new revision: 1.7; previous revision: 1.6 done
Attachment #385380 - Flags: checked‑in+
Alors, FIXED and fixed1.9.1?
Verfied in the snippets that are ready to go - there are nulls for beta and release channels, mn and tr locales, all platforms.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.