From Fedora Project Wiki

(more cleanups - drop the first two 'specifics')
(Release Criteria Specifics)
Line 30: Line 30:
* Make it clear whether a given bug should block the finalization of a release
* Make it clear whether a given bug should block the finalization of a release
== Release Criteria Specifics ==
* Unique pages for the release criteria are created for each public release
* Release criteria not only reflect acceptable defect levels, they also detail required levels of polish
== Public Releases ==
== Public Releases ==

Revision as of 19:31, 7 December 2009

You can't know if you're ready to release unless you know what done means.

When you use release criteria to know when a project is done, you have taken potentially hidden decisions and made them public and clear. Make your release criteria objective and measurable, so everyone on the project knows what they're working towards. Use the criteria as you progress through the project and up to the final release. Then you can say 'Release it!' with pride.

Also, ponies.


The release criteria aim to:

  • Clearly specify the criteria that must be met for each of our public releases (Alpha, Beta, Final) to ship
  • Document all the requirements of our target audience for each Fedora release
    • The target audiences for each public release (Alpha, Beta, and Final) can be different, and may overlap
  • Establish when a release is "done" in terms that most people can understand and in ways that help new people to understand the process and participate


Having a consistent, public and comprehensive set of release critera should:

  • Reduce the need for meetings to be held and subjective decisions made at the last minute
  • Help others who are not involved in the release process to understand our goals and objectives
  • Reduce the need for "gut level" subjective feelings about whether we are ready to ship or not
  • Help us to focus on the purpose of the release and what we are doing it for while focusing less time and energy on things outside of this scope
  • Provide an early warning sign if the release is not on track for shipping on time
  • Make it clear whether a given bug should block the finalization of a release

Public Releases

Release Constraints

Fedora places a high priority on releasing according to schedule. While release quality is very important, there are circumstances where the schedule takes priority.

The following priorities, in this order, will define what matters most in completing our releases:

  1. Target schedule date
  2. Release quality
  3. New release features

Bugs can be fixed in package updates and new features can be included in the next release.

Reference Material