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.

The Release Team is a committee of the GNOME Foundation Board of Directors. It is tasked with determining what constitutes official GNOME software.

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

Current Development

Development schedule and freeze status

Project repository / issue tracker: https://gitlab.gnome.org/GNOME/gnome-build-meta/

Release Team

New project wiki page: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/wikis/home

Here is some information about the GNOME Release Team and process. If you need help, join the #release-team channel on IRC or start a thread in Discourse tagged with release-team. Subscribe to devel-announce-list (archives) for release-team and other developer-related announcements. (The Release Team mailing list is not used anymore since August 2020.)

Release Team Membership
Feature plans for the next GNOME release (no longer used)
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

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 corresponding Milestone for issues which should be fixed.

TODO for this page

Mention the releng module in git.