655376 - Notify authors of passing / upgraded addons after max version bump

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Administration, defect, P1)

Description

[Kumar McMillan [:kumar]]

After fligtar bumps the new max version for bulk-validated addons, each author should be emailed a notice.

What should the default template for the email say?

See bug 651284 for a related feature where addon developers are notified upon failure.  The process in which max versions are bumped is in bug 651294.  Perhaps this feature should be merged with that?

Comment 1

[Justin Scott [:fligtar]]

Subject: {{ADDON_NAME}} compatibility with Firefox 5

Dear add-on author,

Good news! Our automated tests did not detect any compatibility issues with your add-on {{ADDON_NAME}} and Firefox 5. We've updated your add-on's compatibility to work with Firefox 5.* so that our Aurora users can begin using your add-on.

You can view the results of our compatibility check here: {{RESULTS_LINK}}

This compatibility bump is server-side and we did not modify your add-on package in any way.

Though we did not detect any issues, we strongly encourage you to test your add-on in Firefox 5 and review the list of changes here: https://developer.mozilla.org/en/Firefox_5_for_developers

Thank you,

Firefox Add-ons team

--

You are receiving this email as the registered author of {{ADDON_NAME}} on addons.mozilla.org. If you no longer wish to receive these emails, please disable your add-on from the Developer Hub at https://addons.mozilla.org/developers

Comment 2

[Wil Clouser [:clouserw]]

when you do this, all the "Firefox 5" stuff in there should be a variable.  -> andym since he's doing the other email case

Comment 3

[Andy McKay]

Added in https://developer.mozilla.org/firefox_for_developers so we can avoid worrying about version numbers that generate invalid URLs if we had something like https://developer.mozilla.org/en/{{VERSION}}_for_developers.

Comment 4

[Justin Scott [:fligtar]]

These emails are just templates that I'll be changing in the tool before sending them, right? I was planning to update the link each time.

Comment 5

[Andy McKay]

Right. Comment 2, said "make stuff a variable", so I did, but I think this link is also less likely to be easily forgotten about.

Comment 6

[Andy McKay]

https://github.com/jbalogh/zamboni/commit/464148cf8b397653e96d41b2cd6ce77eaf2f721f