Closed Bug 790346 Opened 12 years ago Closed 12 years ago

update release automation docs for new l10n milestone creation processes

Categories

(Release Engineering :: Release Automation: Other, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: armenzg)

References

Details

      No description provided.
This got done by aki:
https://wiki.mozilla.org/index.php?title=Release%3ARelease_Automation_on_Mercurial%3AStarting_a_Release&action=historysubmit&diff=469739&oldid=463974
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
These aren't fully updated. The Fennec and Firefox sections of https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Preparation#Creating_beta_milestones still talk about confirm-ship pages. Those don't exist anymore and appear to be replaced by a "Shipping tools" section on https://l10n.mozilla.org/shipping/about-milestone/fx16_beta_b4 and such.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Priority: -- → P2
Priority: P2 → P3
This needs to be fixed. Our docs aren't correct for Betas, and non-existant for final releases. This caused massive confusion/panic today.
Severity: normal → critical
Priority: P3 → P1
Is https://l10n-dev-sj.mozilla.org/ the right URL? I thought we were using the production system now.

I added this edit, about making sure the beta # is correct: https://wiki.mozilla.org/index.php?title=Release%3ARelease_Automation_on_Mercurial%3AStarting_a_Release&action=historysubmit&diff=478121&oldid=477945

The rest reads OK.
(In reply to Ben Hearsum [:bhearsum] from comment #6)
> Is https://l10n-dev-sj.mozilla.org/ the right URL? I thought we were using
> the production system now.

08:07 < bhearsum> we should be using l10n.m.o for real releases at this point, right?
08:08 < Pike> yes
I fixed that and used l10n.m.o. I was copy/pasting URL from the dev instance since I was tinkering there.

Your edit looks good. Clearer.

Let me know if I missed anything.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 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.