Our docs don't talk about how to do it, even though it's a regular thing now.
Might be good to update the Fennec section as part of this, too: https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Preparation#Fennec I don't think it's all necessary anymore..it talks about maemo-locales
It is necessary; maemo-locales is the leftover name for the file that holds the multilocale locales.
I added the info in https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Starting_a_Release#Creating_beta_milestones We *cannot* rename milestones. Only Axel can.
Summary: update the l10n milestone documentation to include creation/renaming → update the l10n milestone documentation to include creation
Please let me know if the documentation makes sense. If I hear nothing in one week I will close the bug and hope that we can optimize the documentation as people find issues with it from release to release.
From Axel's email: There actually isn't anything like "release" milestones, there are just milestones. The way you create a "release" milestone is that you just go through the regular path, and create milestones for the version that's on beta. (*) They look release-ish if you give them an empty name, first text field, and a code (second text field) that's having a non-postfixed code, i.e. tb14. For the fx/fennec ones, the name is ".0.1", which is pasted after the app version name ("Firefox 14"), and the code is fx14.0.1 etc. That's just manual editing to make them match expectations. There isn't any documentation about release milestones atm, and it sounded like there wasn't a clear handoff in responsibility?
What do we want to do here? Ask Alex/Lukas if the release milestone should be put on Axel's hand and not take responsibility.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 790346
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.