Mobile/Releases/Release Checklist: Difference between revisions

Jump to navigation Jump to search
string freeze, build updates
(string freeze, build updates)
Line 30: Line 30:


=== Get Set ===
=== Get Set ===
* Enact a string freeze - <font color="blue">Project lead</font>
** Verify l10n changesets are updated with latest good l10n revisions
* Enact a code freeze - <font color="red">Dev lead</font>
* Enact a code freeze - <font color="red">Dev lead</font>
** Email mobile-release-drivers when all code is in with formal "Go"
** Determine release branches
** Email mobile-release-drivers when all code is in with formal "Go" (preferably with changesets to avoid checkins slipping in)


* Candidate builds created (all locales) - <font color="green">Build lead</font>
* Candidate builds created (all locales) - <font color="green">Build lead</font>
** Release branches/tagging
** Source tarballs
** Updates
** Email mobile-release-drivers when builds are created
** Email mobile-release-drivers when builds are created


Line 56: Line 63:
# Formal "Go" email sent to mobile-release-drivers - <font color="blue">Project lead</font>
# Formal "Go" email sent to mobile-release-drivers - <font color="blue">Project lead</font>
# Copy builds to releases/ and softlink from multi/dists to dists  - <font color="green">Build lead</font>
# Copy builds to releases/ and softlink from multi/dists to dists  - <font color="green">Build lead</font>
# Bouncer urls - <font color="green">Build lead</font>
# Verify repos show up on moff.mozilla.com and bouncer urls are all in place - <font color="orange">QA Lead</font>
# Verify repos show up on moff.mozilla.com and bouncer urls are all in place - <font color="orange">QA Lead</font>
# <font color="red">Send vulnerability notices - </font><font color="brown">Dev lead</font>
# <font color="red">Send vulnerability notices - </font><font color="brown">Dev lead</font>
Confirmed users
4,971

edits

Navigation menu