Confirmed users
2,816
edits
Release Management: Difference between revisions
m
Moving 2 of the calendar links to the calendar page we link to in this section. It seems redundant.
(add links to mission control and balrog admin interface) |
m (Moving 2 of the calendar links to the calendar page we link to in this section. It seems redundant.) |
||
| Line 5: | Line 5: | ||
* The [[Release_Management/Release_Process | Release Process]] explained | * The [[Release_Management/Release_Process | Release Process]] explained | ||
* [[Releases | Current and Past Releases]] | * [[Releases | Current and Past Releases]] | ||
=About Release Management= | =About Release Management= | ||
The Release Management team keeps the release process on track for upcoming releases. We focus on release quality, security, and stability. As release managers follow specific features and individual bugs, we work with developers, engineering managers, product managers, UI/UX teams, QE, and release engineering, doing whatever it takes to coordinate the many details in the creation of a new version of Firefox. We aim to get features & fixes landed in time for proper evaluation. Our goal is to ship the most stable & excellent product possible for Firefox Desktop & Mobile for our users. | The Release Management team keeps the [[Release_Management/Release_Process | release process]] on track for upcoming releases. We focus on release quality, security, and stability. As release managers follow specific features and individual bugs, we work with developers, engineering managers, product managers, UI/UX teams, QE, and release engineering, doing whatever it takes to coordinate the many details in the creation of a new version of Firefox. We aim to get features & fixes landed in time for proper evaluation. Our goal is to ship the most stable & excellent product possible for Firefox Desktop & Mobile for our users. | ||
= Contribute = | = Contribute = | ||