Closed Bug 847494 Opened 13 years ago Closed 13 years ago

ship it should link to the l10n dashboard

Categories

(Release Engineering :: Release Automation, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 850224

People

(Reporter: bhearsum, Unassigned)

Details

(Whiteboard: [shipit])

Ideally, it would link right to the changesets. However, since we have to create milestones ourselves we may only be able to do as good as linking to the "create milestones" page (https://l10n.mozilla.org/shipping/release/select-milestones/) or the landing page (https://l10n.mozilla.org/shipping/milestones)
Lukas, is linking to one of these pages what you had in mind?
Flags: needinfo?(lsblakk)
Priority: -- → P3
I guess since milestones need to be created (is there any plan for an API where we could create the milestones _as_ the link to the l10n-changesets? or alternately that the milestones are generated on a schedule of some sort like on Tuesday mornings unless manually created?) for now the create milestones page would be preferred if there's fail-safe of not re-creating milestones should they already exist, otherwise the latter option in comment 0.
Flags: needinfo?(lsblakk)
(In reply to lsblakk@mozilla.com from comment #2) > I guess since milestones need to be created (is there any plan for an API > where we could create the milestones _as_ the link to the l10n-changesets? Given how feature requests for release related things have gone, I'm going to assume "no". > or alternately that the milestones are generated on a schedule of some sort > like on Tuesday mornings unless manually created?) for now the create > milestones page would be preferred if there's fail-safe of not re-creating > milestones should they already exist, otherwise the latter option in comment > 0. I went the safe route here and linked to https://l10n.mozilla.org/shipping/milestones as part of bug 850224.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.