884915 - Notify partners automatically when release repacks are ready

Status: NEW

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

Description

[Chris Cooper [:coop] (he/him)]

As part of our post-release steps, we should automatically notify partners that their repacks are ready and where they can find them.

mconnor is putting together a list of the current partner contacts that we can use for notification. Until this list is ready, we could send the notification to release@m.c for testing.

Comment 1

[Mike Connor [:mconnor]]

What's necessary to resolve this?  I'd ideally like to have this working in time for Fx23.

Comment 2

[Chris Cooper [:coop] (he/him)]

Is the email list populated now? If so, I can put together a notification template and add the build step.

Comment 3

[Mike Connor [:mconnor]]

Not yet, have a draft intro email for the people I'm going to add, was figuring we'd test it before we hooked up the list.

Comment 4

[Chris Cooper [:coop] (he/him)]

I think we should be able to plug-in to the existing message framework for releases. Here are my criteria for the message template:

* simple (for obvious reasons)
* make a distinction between betas and final release, i.e. drop the verification wording for final release in the subject and body
* include links to process improvements at the bottom

If having different versions for beta and final release is too hard, I'm fine with using the "verification" text for both.

Here's an example message for a beta release:
>>>
Subject: [release] Firefox 23.0b8 build1: Partner repacks available for verification
 
Hello Mozilla partners,
 
Your partner repacks for the upcoming pre-release (beta) version of Firefox 23.0b8 build1 are available for download for your verification:

http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/23.0b8-candidates/build1/partner-repacks/

Links:
How to submit changes to your partner repack config: https://wiki.mozilla.org/Partnering/Repacks/Submitting_Changes#Creating_a_patch
>>>

Here's the same message for a final release:
>>>
Subject: [release] Firefox 23.0 build1: Partner repacks available

Hello Mozilla partners,
 
Your partner repacks for the upcoming release version of Firefox 23.0 build1 are available for download:

http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/23.0-candidates/build1/partner-repacks/

Links:
How to submit changes to your partner repack config: https://wiki.mozilla.org/Partnering/Repacks/Submitting_Changes#Creating_a_patch
>>>

Comment 5

[Mike Connor [:mconnor]]

The partner list is ready to go for this, for the record.  I think we're past initial builds for 23, but I'd like to get this fully locked down by 24.

Comment 6

[Chris Cooper [:coop] (he/him)]

I've been propping this up with the manual notifications since August, but I don't have the time to deal with automating the solution.

Comment 7

[Chris Cooper [:coop] (he/him)]

mkaply: is this something we still care about? Maybe setup notifications on S3 bucket changes?

Comment 8

[Mike Kaply [:mkaply]]

Yes, definitely something we still care about.

Comment 9

[Chris Cooper [:coop] (he/him)]

Do we want to setup Event Notifications then? This will also catch the case where we respin single partners for late changes.

http://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html#how-to-enable-disable-notification-intro

Comment 10

[Mike Kaply [:mkaply]]

> Do we want to setup Event Notifications then? This will also catch the case where we respin single partners for late changes.

That does look promising. How much work will we have to do to turn those into emails?

Comment 11

[Mihai Tabara [:mtabara]⌚️GMT]

I wonder if this is something we could easily solve in the new TC world now.