Release Planning

The GNOME Release Team helps to coordinate the GNOME release process, mainly by creating a 6-monthly release schedule, and keeping everyone informed about the various stages of that schedule. We work for the developer community, helping everyone to work together and make progress. We try not to get in the way.

Current Development

Unstable: GNOME 2.27 Release Planning

Stable: GNOME 2.26 start page and its release planning

Release Team

Here is some information about the GNOME Release Team and process. If you need help, email the Release Team (archives) or join the #release-team channel on IRC. Subscribe to devel-announce-list (archives) for release-team and other developer-related announcements.

• Release Team Membership

• Documentation of Requirements

  • Freezes (and requesting break approvals)

  • GNOME Module Requirements

  • Proposing New Modules

• Release-team HOWTOs

  • Guide for New Release Team Members

  • How to make a GNOME release

• Old Documents

  • Minutes of Previous Meetings

  • Release Set Descriptions

  • The Time-Based Schedule

  • Release Team Tasks (and Tasks ordered by time in the cycle)

See also Advice for Maintainers.

Testing and Bugs

To help test and refine GNOME, set up a safe testing platform following the TestingGuide and join the GNOME Bugsquad.

Check the 2.26 potential showstopper bug list for things to fix.

TODO for this page

• Mention the releng module in CVS.
• Find what to do about the release team minutes and then remove developer.gnome.org/dotplan (text already moved and redirects already added).