From Fedora Project Wiki

(inital version of page.)
 
Line 23: Line 23:
  
 
== Project members should be able to transparently measure or monitor a new updates process to objectively measure its effectiveness, and determine whether the updates process is achieving the aforementioned vision statements ==
 
== Project members should be able to transparently measure or monitor a new updates process to objectively measure its effectiveness, and determine whether the updates process is achieving the aforementioned vision statements ==
 +
 +
 +
== Add an additional optional repository for feature updates ==
 +
 +
*# By=F14: Have an updates-features optional repository.  The current updates-testing to updates path would be used for all security and bug fixes.  A new updates-features-testing to updates-features will be used for updates that could affect the stability of the release.  This will allow inclusion of upstream projects that do not have their releases in sync with Fedora's.  These repos would not be enabled by default, but by enabling them the user will be able to use the latest releases of their software without having to run rawhide. 
 +
 +
To encourage users to upgrade to the newest releases I suggest these repos be frozen and accept no further pushes once the next release goes into alpha.  So for release (n-1) bug and security fixes only, release (n) bug and security fixes throughout its life, feature updates optional, with no new feature updates after (n+1) goes into alpha.

Revision as of 17:43, 14 June 2010

Ideas for implementing the Boards stable updates vision

Note ideas under each of the vision statement lines that apply to it.

Note if your idea should be targeted at before f14, by f15, or "later"

The update repositories for stable releases of the Fedora distribution should provide our users with a consistent and high quality stream of updates

Stable releases should provide a consistent user experience throughout the lifecycle, and only fix bugs and security issues

    1. BY-F14: Document this stance in maintainer docs and announce to maintainers the new docs.
    2. BY-F14: release managers for each release to monitor updates and educate maintainers?

Stable releases should not be used for tracking upstream version closely when this is likely to change the user experience beyond fixing bugs and security issues

Close tracking of upstream should be done in the Rawhide repo wherever possible, and we should strive to move our patches upstream

More skilled and/or intrepid users are encouraged to use Rawhide along with participating in testing of stable branches during the development and pre-release period

Stable releases, pre-release branches, and Rawhide have a graduated approach to what types of updates are expected. For example, a pre-release branch should accept some updates which a stable release would not, and rawhide would accept updates that are not appropriate for either a stable release or a pre-release

    1. BY-F14: metrics on how many updates each branch gets including rawhide?

Project members should be able to transparently measure or monitor a new updates process to objectively measure its effectiveness, and determine whether the updates process is achieving the aforementioned vision statements

Add an additional optional repository for feature updates

    1. By=F14: Have an updates-features optional repository. The current updates-testing to updates path would be used for all security and bug fixes. A new updates-features-testing to updates-features will be used for updates that could affect the stability of the release. This will allow inclusion of upstream projects that do not have their releases in sync with Fedora's. These repos would not be enabled by default, but by enabling them the user will be able to use the latest releases of their software without having to run rawhide.

To encourage users to upgrade to the newest releases I suggest these repos be frozen and accept no further pushes once the next release goes into alpha. So for release (n-1) bug and security fixes only, release (n) bug and security fixes throughout its life, feature updates optional, with no new feature updates after (n+1) goes into alpha.