Glossary

• Stabilization is the process of backing out and preff-ing off features and changes
• Downstream Repository is the repository from which an antecedent or Upstream Repository is merged to, for instance mozilla-aurora is the downstream repository for mozilla-central in the current

FAQ

Milestones

Q: What are the milestones for FF5?

A: mozilla-aurora merges to mozilla-beta on May 17.  Other milestones are described here

Q: What are the milestones for the release after FF5?

A: The next merge from mozilla-central to mozilla-aurora should occur May 24.

Repositories

Q: What repositories do we use for the rapid release process?

A: mozilla-central, mozilla-aurora, mozilla-beta and mozilla-release described here

Q: What is the Firefox version number used in each repository?

A: mozilla-central uses X.0a1, mozilla-aurora uses X.0a2, mozilla-beta X.0 as described here

Q: What is the gecko version number used in each repository?

A: Same as the Firefox version number as described here

Q: Does mozilla-central require approval flags in bugzilla?

A: No.

Q: Does mozilla-aurora require approval flags in bugzilla?

A: Yes.  There is proposal on dev-planning for this process, you can ask release drivers for approval

Q: How is one repository merged to another?

A: The mechanics are described here

Q: When does stabilization occur?

A: After the pull to the next downstream branch.  For instance mozilla-central is merged to mozilla-aurora and then stabilization occurs on mozilla-aurora.

Triage

Q: How do I nominate a bug for action in the mozilla-aurora repository?

A: Set tracking5?

Q: How do I see what bugs have been nominated and approved?

A: Firefox/Aurora

Channels

Q: What channels exist for updates?

A: Nightly, Aurora, Beta and Release

Q: What locales will be built for the Aurora channel?

A: All 88

Q: What locales will be built for the Beta and Release channel?

A: All locales that have been shipped before or are new and well supported