Release Management/OS EOL: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Criteria for OS EOL = Mozilla bases changes in supported operating systems on: * population size and trends * vendor support * testing resources * technical feasibility of cont...") |
|||
| Line 18: | Line 18: | ||
# Allow time to discuss on those lists | # Allow time to discuss on those lists | ||
# Final call on whether to proceed comes from the Product and Release Management teams | # Final call on whether to proceed comes from the Product and Release Management teams | ||
# Bugs filed for no longer offering updates/installs to the affected OS version | |||
# Timeline for EOL is determined by Release Management and Engineering | # Timeline for EOL is determined by Release Management and Engineering | ||
# Bug filed for hotfix targeted at EOL OS, on | # Bug filed for EOL communication hotfix targeted specifically at EOL OS. Decision must be made at the versions of Firefox we target with the communication (all, or last version before EOL) | ||
# Test the hotfix on the Beta population, at least one cycle prior to EOL | |||
# Either leave up the beta hotfix or roll out a release version at least a cycle before EOL | |||
# Blog about the decision at least a cycle before EOL | |||
= Past EOL Efforts = | = Past EOL Efforts = | ||
* {{bug|741004}} – Create a hotfix add-on to communicate the FF13 de-support | * {{bug|741004}} – Create a hotfix add-on to communicate the FF13 de-support | ||
* {{bug|774509}} – We need to communicate the FF17 OS X 10.5 EOL to our users (add-on hotfix) | * {{bug|774509}} – We need to communicate the FF17 OS X 10.5 EOL to our users (add-on hotfix) | ||
Revision as of 18:44, 18 October 2012
Criteria for OS EOL
Mozilla bases changes in supported operating systems on:
- population size and trends
- vendor support
- testing resources
- technical feasibility of continued support
Drivers
- Team asking for EOL of an OS
- Product Team - Asa Dotzler
- Marketing - Laura Forrest
- Release Management - Alex Keybl, Lukas Blakk, or Bhavana Bajaj
- PR - Mark Lavine or Erica Jostedt
- Add-on Hotfix lead - determined on a per-hotfix basis
Steps for EOL
- Team asks for EOL consideration on dev-planning and dev-platform, with justification based upon the criteria above. This must happen at least 3 cycles prior to desired EOL.
- Allow time to discuss on those lists
- Final call on whether to proceed comes from the Product and Release Management teams
- Bugs filed for no longer offering updates/installs to the affected OS version
- Timeline for EOL is determined by Release Management and Engineering
- Bug filed for EOL communication hotfix targeted specifically at EOL OS. Decision must be made at the versions of Firefox we target with the communication (all, or last version before EOL)
- Test the hotfix on the Beta population, at least one cycle prior to EOL
- Either leave up the beta hotfix or roll out a release version at least a cycle before EOL
- Blog about the decision at least a cycle before EOL
Past EOL Efforts
- bug 741004 – Create a hotfix add-on to communicate the FF13 de-support
- bug 774509 – We need to communicate the FF17 OS X 10.5 EOL to our users (add-on hotfix)