The release-automation for FF3.0.x sends status emails (step completion, etc) to email@example.com. However, we are all on firstname.lastname@example.org, so emails should go there instead. Please change automation to use email@example.com, in preparation for moving any remaining community folks on firstname.lastname@example.org over to email@example.com.
Created attachment 389718 [details] [diff] [review] send emails to firstname.lastname@example.org for 1.9.0 releases Here is the list of files where email@example.com is being used in case we want to make more changes: ./buildbot-configs/automation/staging/master.cfg ./buildbot-configs/automation/staging/tb-master.cfg ./release/configs/fx-moz18-bootstrap.cfg ./release/configs/fx-moz180-bootstrap.cfg ./release/configs/fx-moz19-bootstrap.cfg ./release/configs/tb-moz18-bootstrap.cfg ./release/configs/tb-moz180-bootstrap.cfg ./release/configs/xr-moz19-bootstrap.cfg ./tinderbox-configs/firefox/linux/tinder-config.pl ./tinderbox-configs/firefox/macosx/tinder-config.pl ./tinderbox-configs/firefox/win32/tinder-config.pl ./tinderbox-configs/seamonkey/linux/tinder-config.pl ./tinderbox-configs/sunbird/macosx/tinder-config.pl ./tinderbox-configs/thunderbird/macosx/tinder-config.pl ./tinderbox-configs/xulrunner/win32/tinder-config.pl
Attachment #389718 - Flags: review?(joduinn)
Don't forget to check the release and l10n_release branches for all of those tinder-config.pl files - they're the ones that are used for Firefox 3.0.x releases.
I checked the branches l10n, release and release_l10n and the email is only being used for thunderbird and xulrunner
From what I can tell from the tinderbox code, $BuildAdministrator only appears in logs and doesn't cause any actual mail. So I wouldn't be worried about modifying all the tinderbox configs. (There are many more instances than you found, because in some places we use "build\@mozilla.org"). We could ignore the old bootstrap configs too, and just change release/configs/tb-moz18-bootstrap.cfg release/configs/fx-moz19-bootstrap.cfg release/configs/xr-moz19-bootstrap.cfg
9 years ago
Attachment #389718 - Flags: review?(joduinn) → review+
Putting it into the queue since I won't be touching it anytime before 2 weeks.
Assignee: armenzg → nobody
Component: Release Engineering → Release Engineering: Future
Priority: P3 → --
Summary: Have release-automation send notifications to firstname.lastname@example.org → Have release-automation (Fx3.0/1.9.0) send notifications to email@example.com
Component: Release Engineering: Future → Release Engineering
Created attachment 421689 [details] [diff] [review] Update all bootstrap configs I'll take a look at the blat config for the windows boxes too.
Assignee: nobody → nrthomas
Attachment #421689 - Flags: review?(bhearsum)
(In reply to comment #7) > I'll take a look at the blat config for the windows boxes too. This is a red herring.
Attachment #421689 - Flags: review?(bhearsum) → review+
Comment on attachment 421689 [details] [diff] [review] Update all bootstrap configs If this gets spammy then main person driving the release can be in 'to' and set cc to joduinn to keep him in the loop.
Attachment #421689 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Last Resolved: 9 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.