Closed Bug 745968 Opened 12 years ago Closed 8 years ago

Pulse notifications for l10n beta candidate builds should include 'l10n' instead of 'repack'

Categories

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

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: whimboo, Unassigned)

References

Details

Recently I have setup our Mozmill CI system to run the BFT tests against beta candidate builds of Firefox. This works fine for en-US builds by watching the 'release-mozilla-beta' branch.

What I have noticed is that I don't get any notification for localized beta candidate builds. Those notification should be send out for the same branch like the en-US builds.
we are sending out the notifications for release repacks, they're just structured differently.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
As talked with Chris on IRC a change from 'repack' to 'l10n' should be possible. But it's probably not a good idea to make this change now. We should wait until separate notifications can be send out by the repack machines for each individual locale. I will file this bug shortly.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Missing Pulse notification for l10n beta candidate builds → Pulse notifications for l10n beta candidate builds should include 'l10n' instead of 'repack'
Depends on: 745975
Assignee: nobody → sbruno
Product: mozilla.org → Release Engineering
The plan is to work on this next week (16-20 September).
Assignee: sbruno → nobody
We might get this for free with release promotion.
Do we still need this?
Flags: needinfo?(hskupin)
I feel that we are stuck with the repack term also in release promotion. So lets keep it and don't worry about this minor thing.
Status: REOPENED → RESOLVED
Closed: 12 years ago8 years ago
Flags: needinfo?(hskupin)
Resolution: --- → WONTFIX
Thank you!
You need to log in before you can comment on or make changes to this bug.