AMO:Updating: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Clouserw moved page AMO/Updating to AMO:Updating: consistency)
(Updating AMO push docs to new weekly format)
 
Line 4: Line 4:
=== Pushing to Production ===
=== Pushing to Production ===


Pushes to production happen once a month on the Thursday of the second full week in the month at 11am Pacific. Code freezes happen the Friday before and a tag is made. This is probably best illustrated with an example:
Pushes to production happen every Thursday at 9am Pacific. Code freezes every Tuesday.


                              2014
You can find our docs on push duty, who is responsible, etc. on https://addons.readthedocs.org/en/latest/server/push-duty.html and by reading the https://mail.mozilla.org/pipermail/dev-addons mailing list where we send tag and push emails every week.
        January              February              March         
  Su Mo Tu We Th Fr Sa  Su Mo Tu We Th Fr Sa  Su Mo Tu We Th Fr Sa 
            1  2  3  4                    1                    1 
  5  6  7  8  9 10 11  2  3  4  5  6  7  8  2  3  4  5  6  7  8 
  12 13 14 15 16 17 18  9 10 11 12 13 14 15  9 10 11 12 13 14 15 
  19 20 21 22 23 24 25  16 17 18 19 20 21 22  16 17 18 19 20 21 22 
  26 27 28 29 30 31    23 24 25 26 27 28    23 24 25 26 27 28 29 
                                              30 31
 
Let's say it is January 21st.  The actions of that day are for developers to close bugs and put them in the 2014-02 milestone (because they will be going live in February of 2014).  For QA, they should be checking the 2014-02 milestone for RESOLVED but not VERIFIED bugs and verifying them.  This will keep there from being a big pile of bugs to verify right before a push.
 
On February 7th (the Friday before the push) we will ensure HEAD is stable and tag it with the date of our next push.  In this case, the tag would be 2014.02.13. If we need to modify that tag between the 7th and 13th we delete the tag and replace it.  If we need to push twice on the same day, we add -2, -3, etc. to the end of the tag.  Once the tag is made we push it to stage (addons.allizom.org) and notify QA to verify the site is correct.
 
If QA finds any blockers on stage they should be fixed immediately, cherry-picked to the tag, and put on stage for verification.
 
On February 13th we push the tag to production.  QA verifies it in production, and we do it all again the next month.


Questions?  Come to #amo on irc.mozilla.org.
Questions?  Come to #amo on irc.mozilla.org.

Latest revision as of 14:16, 5 November 2015

Updating

The AMO update process is as follows:

Pushing to Production

Pushes to production happen every Thursday at 9am Pacific. Code freezes every Tuesday.

You can find our docs on push duty, who is responsible, etc. on https://addons.readthedocs.org/en/latest/server/push-duty.html and by reading the https://mail.mozilla.org/pipermail/dev-addons mailing list where we send tag and push emails every week.

Questions? Come to #amo on irc.mozilla.org.

Retrieved from "https://wiki.allizom.org/index.php?title=AMO:Updating&oldid=1104341"