|
|
| Line 1: |
Line 1: |
| This proposal aims to address updates from a User, not a developer, perspective.
| |
|
| |
|
| Terminology:
| |
| * Release N+2: aka Rawhide, the code base planned for release in 6-12 months.
| |
| * Release N+1: The code base currently branched from rawhide, under active development. (e.g. Fedora 13)
| |
| * Release N: The latest stable release currently advertised. (e.g. Fedora 12)
| |
| * Release N-1: The previous stable release, still capable of receiving updates. (e.g. Fedora 11)
| |
|
| |
| == Expectations by release ==
| |
| # Users expect major package updates in Release N+2, as well as closely following upstream releases.
| |
| # Users expect major package updates in Release N+1. While in development, both major and minor bug fixes, and behavioral changes are expected. After the Feature Freeze, these should be minimized.
| |
| # Users expect updates for Release N to include bug fixes, minor package updates, and minimal changes in functionality.
| |
| ## Major Desktop environment upgrades would be unexpected.
| |
| ## Library soname bumps would be unexpected, and should be the exception, not the rule.
| |
| # Users expect updates for Release N-1 to be restricted to major bug fixes only. No major package updates, change in functionality, library soname bumps, or behavioral changes.
| |
| ## Major Desktop environment upgrades are unexpected and must be avoided.
| |
| ## Library soname bumps are unexpected and must be avoided.
| |
