Thunderbird/Release Driving/Rapid Release Activities

Week 1 begins on the Tuesday of the Release & Merge.

Week 1

• Monday: Merge repositories, comm-aurora - > comm-beta, comm-central -> comm-aurora.
• Tuesday: No drivers meeting due to release activities
• Tuesday: Release builds from previous cycles
• Tuesday/Wednesday: Go for beta 1 (depends on FF completing merge) (beta release procedure)
• By Friday (typically Thursday): Release beta 1
• By Friday: Revise initial features list for comm-aurora.
• By Friday: Prepare compatibility bump for the new comm-aurora build.

Week 2

• Tuesday/Wednesday: Possible go for beta 2 (beta release procedure)
• Thursday/Friday: Release beta 2

Week 3

• Tuesday/Wednesday: Possible go for beta 3 (beta release procedure)
• Thursday/Friday: Release beta 3

Week 4

• Tuesday/Wednesday: Possible go for beta 4 (beta release procedure)
• Thursday/Friday: Release beta 4
• By Friday: Complete compatibility bump for the aurora build.

Week 5

• Tuesday: Final copy of whats new for website.
• Tuesday: Confirm expected list of features for aurora release.
• Tuesday/Wednesday: Possible go for beta 5 (beta release procedure)
• Thursday/Friday: Release beta 5

Week 6

• Tuesday: Final copy of release notes for website (release copy)
• Tuesday/Wednesday: Possible go for final beta (beta 6) (beta release procedure)
• Thursday/Friday: Merge repositories, comm-beta - > comm-release
• Thursday/Friday: Release final beta (beta 6)
• By Thursday: Complete beta copy for the release currently on aurora
• By Monday: Check that bugs landed have the right milestones

Notes

• Betas are considered on a week-by-week basis depending on what patches have landed in comm-beta, mozilla-beta and l10n repositories. Confirmation of a no-beta will also be sent.