Confirmed users
14,525
edits
(→ESR) |
|||
| Line 671: | Line 671: | ||
* Day 42 (Tuesday) | * Day 42 (Tuesday) | ||
** Release Management migrates mozilla-beta to mozilla-release and sends the go to build the next Release | ** Release Management migrates mozilla-beta to mozilla-release and sends the go to build the next Release | ||
== Priorities == | |||
= ESR = | |||
== Timeline == | |||
* Day 0..36 | |||
** QA focuses on verifying most critical and security fixes using the nightly builds | |||
* Day 37 (Thursday) | |||
** Release Management sends the go-to-build for the ESR Candidates | |||
** Release Engineering generates the ESR builds (takes several hours) | |||
** Release Management informs the Enterprise mailing list to start conducting internal integration testing | |||
* Day 38 (Friday) | |||
** QA runs Mozmill-Ondemand functional automation, update automation on the ''esrtest'' channel and update automation on the ''releasetest'' channel | |||
** QA coordinates Sunday night testing of the ESR candidates via email to Softvision | |||
* Day 41 (Monday) | |||
** Softvision completes all of their requisite testing | |||
* Day 42 (Tuesday) | |||
** QA sends final sign-off for release via email to the Release Drivers | |||
** Release Management sends the go to push snippets live | |||
** Release Engineering pushes ESR snippets live and sends email to the Release Drivers when complete | |||
** QA runs Mozmill-ondemand update automation on the ''release'' channel then sends a sign-off email to Release Drivers when complete | |||
== Priorities == | |||