Sumo/Desktop Release Checklist: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(First edit!)
 
(category -> Support Archive)
 
(21 intermediate revisions by one other user not shown)
Line 1: Line 1:
WORK IN PROGRESS -  DRAFT DRAFT DRAFT!
'''WORK IN PROGRESS -  DRAFT DRAFT DRAFT!'''


* 3 weeks before release, look at Erin Lancaster's Firefox cross-functional deck, the beta and release notes to determine list of features that are new and modified
= Checklists =
* 2 weeks before release finish English Language SUMO articles and set to ready for localization
 
* 1 week before release prepare Social FAQ and canned responses and check that features haven't been removed or disabled. If so, update the English Language SUMO articles
* [[SUMO/Desktop_Release_Checklist/Firefox 55 Desktop Release Checklist]]
 
= Checklist template =
'''`*` denotes employee-only material''' (which I think over 90% could be at least open to NDA'd volunteers)
'''BEGIN DESKTOP CHECKLIST'''
 
= Before the release =
* 3 weeks before release, look at [https://docs.google.com/presentation/d/1xluJDxyqncGGn3He5QUvO27oBmZQLyeUuzWiaSnxM3U/edit#slide=id.g1bec37107d_2_161 Erin Lancaster's Firefox cross-functional deck]* and Marketing's Go To Market Deck [https://docs.google.com/presentation/d/1_vzRpWslWWDLiZebtnAr5iZdVtfbsv2lskWAjTj29pQ/edit#slide=id.g2492974c67_0_1 e.g. 55 Go To Market*], test the beta (we all should be testing the beta and nightly at all times right :-) !) and release notes to determine list of features that are new and modified
* 2 weeks before release finish (get legal, marketing and engineering approval(s) if necessary) English Language SUMO articles and set to ready for localization
* 1 week before release prepare Social FAQ and canned responses and check that features haven't been removed or disabled. If so, update the English Language SUMO articles. Share with Social Team and PR and MarComms
* 1 week before release, prepare for SUMO day
* 1 week before release, prepare for SUMO day
* 1 week before release, post thread about the release with new and modified SUMO articles to the SUMO contributor forum


After the release:
= After the release:=
* day of release and day after check SUMO forums for trending issues
* day of release and day after check SUMO forums for trending issues
* the Monday after release check SUMO forums for trending issue
* the Monday after release check SUMO forums for trending issues
* 1 week after release, run a SUMO day
* 1 week after release, run a SUMO day
* 3 weeks after release prepare a SUMO support report
* 3 weeks after release prepare a SUMO support report
'''END DESKTOP CHECKLIST'''
= META FAQ =
* Q: Why is this on wiki.mozilla.org? A: because it is open, editable and discoverable by all  unlike Google Docs, trello, taiga, etc
* Q: Who is the audience for this checklist? A: Everybody not just SUMO folks! Namely: ALL MoFo, MoCo staff and volunteers not just SUMO staff and volunteers. This way everybody is exposed to the incredible :-) amount of yak shaving we have to do around releases.
* Q: How will this Checklist be used? A: This wiki page will be used to manually create public Trello cards. And then from checklist for that release we will link to the cards for that release. e.g. the [[SUMO/Desktop_Release_Checklist/Firefox_55_Desktop_Release_Checklist|Firefox 55 desktop checklist]] will link to the 55 desktop release Trello cards
[[Category:Support Archive]]

Latest revision as of 08:56, 10 June 2021

WORK IN PROGRESS - DRAFT DRAFT DRAFT!

Checklists

Checklist template

`*` denotes employee-only material (which I think over 90% could be at least open to NDA'd volunteers)

BEGIN DESKTOP CHECKLIST

Before the release

  • 3 weeks before release, look at Erin Lancaster's Firefox cross-functional deck* and Marketing's Go To Market Deck e.g. 55 Go To Market*, test the beta (we all should be testing the beta and nightly at all times right :-) !) and release notes to determine list of features that are new and modified
  • 2 weeks before release finish (get legal, marketing and engineering approval(s) if necessary) English Language SUMO articles and set to ready for localization
  • 1 week before release prepare Social FAQ and canned responses and check that features haven't been removed or disabled. If so, update the English Language SUMO articles. Share with Social Team and PR and MarComms
  • 1 week before release, prepare for SUMO day
  • 1 week before release, post thread about the release with new and modified SUMO articles to the SUMO contributor forum

After the release:

  • day of release and day after check SUMO forums for trending issues
  • the Monday after release check SUMO forums for trending issues
  • 1 week after release, run a SUMO day
  • 3 weeks after release prepare a SUMO support report

END DESKTOP CHECKLIST

META FAQ

  • Q: Why is this on wiki.mozilla.org? A: because it is open, editable and discoverable by all unlike Google Docs, trello, taiga, etc
  • Q: Who is the audience for this checklist? A: Everybody not just SUMO folks! Namely: ALL MoFo, MoCo staff and volunteers not just SUMO staff and volunteers. This way everybody is exposed to the incredible :-) amount of yak shaving we have to do around releases.
  • Q: How will this Checklist be used? A: This wiki page will be used to manually create public Trello cards. And then from checklist for that release we will link to the cards for that release. e.g. the Firefox 55 desktop checklist will link to the 55 desktop release Trello cards