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.

We've tried to write down what we consider our mission, here.

Current Development

Unstable: Release Planning for the Next Release

Stable: Notes for the Current Stable Release

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

• Feature plans for the next GNOME release

• Documentation of Requirements

  • Freezes (and requesting break approvals)

  • GNOME Module Requirements (less applicable as moduleset got reorganized for 3.0)

• Release-team HOWTOs

  • Guide for New Release Team Members

  • How to make a GNOME release

• Release Team tasks

• In progress documents

  • Build Failure Policy

  • Release process in other projects

• Old Documents

  • Proposing New Modules (not used since 3.0)

  • Minutes of Previous Meetings

  • Release Set Descriptions

  • The Time-Based Schedule

  • 3.0 Release Day planning; related Marketing document

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 3.24 potential showstopper bug list for things to fix.

Non-empty showstopper bug lists for previous releases:

• 3.22

• 3.20

TODO for this page

• Mention the releng module in git.