GNOME 2.13.x Development Series
GNOME 2.13.x is an unstable development series intended for testing and hacking purposes. GNOME uses odd minor version numbers to indicate development status, so this unstable 2.13.x series will eventually become the official 2.14 stable release. There are many ways you can get involved.
Plans for this release are documented on the RoadMap page. These plans do not necessarily cover every module and every feature that will be worked on, nor are they guaranteed to arrive in time. Maintainers, please keep the RoadMap page up to date where you can. 
When we are near feature-freeze, please mention the new features for the /ReleaseNotes.
Important information for module maintainers:
- Tarballs are due by 23:59 UTC on the Monday specified
- Freezes begin by 23:59 UTC on the Monday specified
- If possible, try to make releases no sooner than 3 days before the tarballs are due. If you need to release early, a simple notification to gnome-i18n and gnome-doc-list would be helpful.
Branching practices, including who to email; also, please make sure everyone knows what branch you are using for the release if you aren't using HEAD
There's a MaintainersCorner wiki page with general helpful information
Release Suites
Schedule
An iCal file is available at http://www.gnome.org/start/unstable/schedule.ics
Week |
Date |
Task |
Notes |
March |
|||
|
September 5th |
GNOME 2.12.0 Tarballs Due |
|
|
September 7th |
GNOME 2.12.0 Final Release! |
|
1 |
September 12th |
|
|
2 |
September 19th |
|
|
3 |
September 26th |
|
|
October |
|||
4 |
October 3rd |
GNOME 2.12.1 Tarballs Due |
|
October 5th |
GNOME 2.12.1 Stable Release |
|
|
5 |
October 10th |
|
|
6 |
October 17th |
|
|
7 |
October 24th |
GNOME 2.13.1 Tarballs Due |
Propose new modules for inclusion! |
October 26th |
GNOME 2.13.1 Development Release |
||
8 |
October 31st |
|
|
November |
|||
9 |
November 7th |
|
|
10 |
November 14th |
GNOME 2.13.2 Tarballs Due |
|
November 16th |
GNOME 2.13.2 Development Release |
|
|
11 |
November 21st |
|
|
12 |
November 28th |
GNOME 2.12.2 Tarballs Due |
|
November 30th |
GNOME 2.12.2 Stable Release |
|
|
December |
|||
13 |
December 5th |
|
|
14 |
December 12th |
GNOME 2.13.3 Tarballs Due |
|
December 14th |
GNOME 2.13.3 Development Release |
|
|
15 |
December 19th |
|
|
16 |
December 26th |
|
|
January |
|||
17 |
January 2nd |
GNOME 2.13.4 Tarballs Due |
String Change Announcement Period: All string changes must be announced to both gnome-i18n@ and gnome-doc-list@. |
January 4th |
GNOME 2.13.4 Development Release |
||
18 |
January 9th |
|
|
19 |
January 16th |
GNOME 2.13.5 Tarballs Due |
API/ABI Freeze: developer APIs should be frozen at this point. |
January 18th |
GNOME 2.13.5 Development Release |
||
20 |
January 23rd |
|
|
21 |
January 30th |
GNOME 2.14.0 Beta 1 (2.13.90) Tarballs Due |
UI Freeze: No UI changes may be made without approval from the release-team and notification to the GDP. |
February 1st |
GNOME 2.14.0 Beta 1 (2.13.90) |
||
February |
|||
22 |
February 6th |
GNOME 2.12.3 Tarballs Due |
|
February 8th |
GNOME 2.12.3 Stable Release |
||
23 |
February 13th |
GNOME 2.14.0 Beta 2 (2.13.91) Tarballs Due |
String Freeze: no string changes may be made without confirmation from the l10n team (gnome-i18n@) and notification to both the release team and the GDP (gnome-doc-list@). |
February 15th |
GNOME 2.14.0 Beta 2 (2.13.91) |
||
24 |
February 20th |
|
|
25 |
February 27th |
GNOME 2.14.0 Release Candidate (2.13.92) Tarballs Due |
|
March 1st |
GNOME 2.14.0 Release Candidate (2.13.92) |
|
|
March |
|||
26 |
March 6th |
|
Hard Code Freeze: no source code changes can be made without approval from the release-team. Translation and documentation can continue. |
27 |
March 13th |
GNOME 2.14.0 Tarballs Due |
Hard Code Freeze ends, but other freezes remain in effect for the stable branch. |
March 15th |
GNOME 2.14.0 Final Release! |
|
|
|
March 20th |
|
|
|
March 27th |
|
|
April |
|||
|
April 3rd |
|
|
|
April 10th |
GNOME 2.14.1 Tarballs Due |
|
April 12th |
GNOME 2.14.1 Final Release |
|
|