678082 - please notify socorro-dev when releases are pushed

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect, P4)

Description

[Robert Helmer [:rhelmer]]

Re: bug 674793 comment 8, we are able to gather some but not all of the info we need to associate betas with build IDs from FTP (mobile is the main problem right now, see bug 675272). We should be able to automatically keep up with Firefox, Thunderbird, SeaMonkey though.

Can [e-mail] get an automatic email notification when releases go out? I know there are better systems in the works, but we need to make sure we can do at least manual updates in the meantime.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

We should be able to automate email like that, either after the builds complete, or when pushing to the mirrors. I'd suggest the former since QA and other people are picking up builds from the candidates directories on ftp.m.o pretty much straight away. Would you prefer one per build, or just one email with all buildIDs ? We should send this info to metrics too.

Which releases are you missing information for ? Build notes like
  https://wiki.mozilla.org/Releases/Firefox_6.0b5/BuildNotes
might help, or we might have things stashed away somewhere.

Comment 2

[Robert Helmer [:rhelmer]]

(In reply to Nick Thomas [:nthomas] from comment #1)
> We should be able to automate email like that, either after the builds
> complete, or when pushing to the mirrors. I'd suggest the former since QA
> and other people are picking up builds from the candidates directories on
> ftp.m.o pretty much straight away. Would you prefer one per build, or just
> one email with all buildIDs ? We should send this info to metrics too.


Whichever is easier for you is fine. Offhand I'd say one email with all buildIDs would be nicer for us.


> Which releases are you missing information for ? Build notes like
>   https://wiki.mozilla.org/Releases/Firefox_6.0b5/BuildNotes
> might help, or we might have things stashed away somewhere.


Per bug 675272 comment 3, I was able to backfill everything ok, but until that's fixed we'll need to add mobile releases by hand. Really the only thing blocking us from getting the info we need from FTP is bug 675272.

Comment 3

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

after quick meeting w/Laura

(In reply to Robert Helmer [:rhelmer] from comment #2)
> Can [e-mail] get an automatic email notification when
> releases go out? I know there are better systems in the works, but we need
> to make sure we can do at least manual updates in the meantime.

1) We already send an automated email to release-drivers@ for all significant steps of the release automation process. Being on release-drivers@ and filtering for [release] is one way to solve this need, and had added benefits of you knowing if anything comes up to block/respin a release-in-progress. However, we can happily adjust automation to also send an email to socorro-dev@m.c as well if you prefer to not signup for release-drivers.

2) If you still want an email sent specifically to socorro-dev@, can you be more specific on *which* specific milestone in the release automation you want it? Before we start tagging? After handing builds to QA? After handing updates to QA?...

Comment 4

[Robert Helmer [:rhelmer]]

(In reply to John O'Duinn [:joduinn] from comment #3)

1) I don't think all the socorro devs would want to be on release-drivers, I'd be worried about missing a notice if we did it this way so would prefer socorro-dev@m.c

I took a look at these emails and they don't contain the build ID. Is it possible for them to?

2) Actually really we only need mobile (until bug 675272 is fixed), and we should ideally just get one notice when it's posted to FTP.

Just to distill the earlier comments and bugs linked here, what we are after is associating beta number and build ID for a particular product+version. We can get this info via FTP for everything except mobile due to bug 675272, so fixing that bug would preclude having to email us at all :)

Comment 5

[Lukas Blakk [:lsblakk] use ?needinfo]

> 
> 2) Actually really we only need mobile (until bug 675272 is fixed), and we
> should ideally just get one notice when it's posted to FTP.
> 
> Just to distill the earlier comments and bugs linked here, what we are after
> is associating beta number and build ID for a particular product+version. We
> can get this info via FTP for everything except mobile due to bug 675272, so
> fixing that bug would preclude having to email us at all :)

Looks like now that we have info.txt files for mobile release builds we can take emailing socorro-dev out of the release steps. Resolving and adjusting our release notes template to reflect this.