GNOME 2.27.x/2.29.x Development Series
GNOME 2.27.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.27.x series will eventually become the official 2.28 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 SVN Trunk
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
Comments/Discussion:
- Please do not add comments here. Keep any discussion streamlined on desktop-devel mailing list.
Week |
Date |
Task |
Notes |
Cleanup targets |
March |
||||
-2 |
Mar 02 |
|
Start of new (app) modules proposal period |
|
0 |
Mar 16 |
GNOME 2.26.0 stable tarballs due |
|
|
Mar 18 |
GNOME 2.26.0 stable release |
|
|
|
April |
||||
4 |
Apr 13 |
GNOME 2.26.1 stable tarballs due |
|
ZERO modules with Glib-Deprecated-Symbols. Means: Yelp must be fixed. |
Apr 15 |
GNOME 2.26.1 stable release |
|
|
|
May |
||||
7 |
May 4 |
GNOME 2.27.1 unstable tarballs due |
|
Officially announce libglade as deprecated in favor of GtkBuilder after important bugs (like 553385) have been identified and fixed (Tracker bug). |
May 6 |
GNOME 2.27.1 unstable release |
|
|
|
9 |
May 18 |
GNOME 2.26.2 stable tarballs due |
End of new (app) modules proposal period |
|
May 20 |
GNOME 2.26.2 stable release |
|
|
|
10 |
May 25 |
GNOME 2.27.2 unstable tarballs due |
|
Less than 35 modules depending on libglade. |
May 27 |
GNOME 2.27.2 unstable release |
|
|
|
June |
||||
13 |
Jun 15 |
GNOME 2.27.3 unstable tarballs due |
|
Less than 12 modules depending on libgnome. |
Jun 17 |
GNOME 2.27.3 unstable release |
|
|
|
15 |
Jun 29 |
GNOME 2.26.3 stable tarballs due |
|
|
July |
||||
15 |
Jul 01 |
GNOME 2.26.3 stable release |
|
|
17 |
Jul 13 |
GNOME 2.27.4 unstable tarballs due |
String Change Announcement Period: All string changes must be announced to both gnome-i18n@ and gnome-doc-list@. |
Less than 20 modules depending on libglade. |
Jul 15 |
GNOME 2.27.4 unstable release |
|
|
|
18 |
Jul 20 |
|
API/ABI Freeze for 2.27.x: developer APIs should be frozen at this point. |
|
19 |
Jul 27 |
GNOME 2.27.5 unstable tarballs due |
Feature and Module Freeze: new modules and functionality are chosen now. |
Less than 9 modules depending on libgnome. |
Jul 29 |
GNOME 2.27.5 unstable release |
|
|
|
August |
||||
20 |
Aug 03 |
|
New APIs must be fully documented |
|
21 |
Aug 10 |
GNOME 2.27.90 beta tarballs due |
UI Freeze: No UI changes may be made without approval from the release-team and notification to the GDP (gnome-doc-list@) |
Only modules with low Gtk-Deprecated-Symbols allowed (except for those modules that require API breakage to fix, e.g. Evolution-Data-Server). |
Aug 12 |
GNOME 2.27.90 beta release |
|
|
|
23 |
Aug 24 |
GNOME 2.27.91 beta 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@). |
gnome-shell beta release. Also see this thread. --> OwenTaylor. |
Aug 26 |
GNOME 2.27.91 beta release |
|
|
|
September |
||||
25 |
Sep 07 |
GNOME 2.27.92 rc tarballs due |
|
|
Sep 09 |
GNOME 2.27.92 rc release |
|
|
|
26 |
Sep 14 |
|
Hard Code Freeze: no source code changes can be made without approval from the release-team. Translation and documentation can continue. |
|
27 |
Sep 21 |
GNOME 2.28.0 newstable tarballs due |
Hard Code Freeze ends, but other freezes remain in effect for the stable branch. |
|
Sep 23 |
GNOME 2.28.0 newstable release |
|
|
Week |
Date |
Task |
Notes |
Cleanup targets |
August 2009 |
||||
-6 |
Aug 10 |
|
Start of new (app) modules proposal period for 2.30 |
|
September 2009 |
||||
0 |
Sep 21 |
GNOME 2.28.0 stable tarballs due |
|
|
Sep 23 |
GNOME 2.28.0 stable release |
|
|
|
October |
||||
4 |
Oct 19 |
GNOME 2.28.1 stable tarballs due |
|
|
Oct 21 |
GNOME 2.28.1 stable release |
|
|
|
5 |
Oct 26 |
GNOME 2.29.1 unstable tarballs due |
End of new (app) modules proposal period |
ZERO modules with Gtk-Deprecated-Symbols. We try to break API now wherever required (e.g. for Evolution-Data-Server). |
Oct 28 |
GNOME 2.29.1 unstable release |
|
|
|
November |
||||
6 |
Nov 2 |
|
Release Team meets about new module decisions for 2.30 with community input up to this point. |
|
7 |
Nov 9 |
|
Module Freeze: new modules for 2.30 are chosen now. |
|
8 |
Nov 16 |
GNOME 2.29.2 unstable tarballs due |
|
New a11y infrastructure must be in place. If there will be regressions we define them now and clearly announce them in advance for 3.0. |
Nov 18 |
GNOME 2.29.2 unstable release |
|
|
|
10 |
Nov 30 |
GNOME 2.29.3 unstable tarballs due |
|
ZERO modules depending on gnome-canvas. Means: Evolution, gtkhtml, anjuta. |
December |
||||
10 |
Dec 02 |
GNOME 2.29.3 unstable release |
|
|
12 |
Dec 14 |
GNOME 2.28.2 stable tarballs due |
|
|
Dec 16 |
GNOME 2.28.2 stable release |
|
|
|
13 |
Dec 21 |
GNOME 2.29.4 unstable tarballs due |
|
ZERO modules (except for libglade) depending on Bonobo/Orbit. |
Dec 23 |
GNOME 2.29.4 unstable release |
|
|
|
January 2010 |
||||
16 |
Jan 11 |
GNOME 2.29.5 unstable tarballs due |
String Change Announcement Period: All string changes must be announced to both gnome-i18n@ and gnome-doc-list@. |
ZERO modules depending on libglade. All modules must have migrated from libglade to GtkBuilder. |
Jan 13 |
GNOME 2.29.5 unstable release |
|
|
|
17 |
Jan 18 |
|
API/ABI Freeze for 2.29.x: developer APIs should be frozen at this point. |
|
18 |
Jan 25 |
GNOME 2.29.6 unstable tarballs due |
Feature Freeze: new functionality is chosen now. |
|
Jan 27 |
GNOME 2.29.6 unstable release |
|
|
|
February |
||||
19 |
Feb 01 |
|
New APIs must be fully documented |
|
20 |
Feb 08 |
GNOME 2.29.90 beta tarballs due |
UI Freeze: No UI changes may be made without approval from the release-team and notification to the GDP (gnome-doc-list@) |
|
Feb 10 |
GNOME 2.29.90 beta release |
|
|
|
22 |
Feb 22 |
GNOME 2.29.91 beta 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@). |
GTK and Glib 3 must be released. |
Feb 24 |
GNOME 2.29.91 beta release |
|
|
|
March |
||||
24 |
Mar 08 |
GNOME 2.29.92 rc tarballs due |
|
|
Mar 10 |
GNOME 2.29.92 rc release |
|
|
|
25 |
Mar 15 |
|
Hard Code Freeze: no source code changes can be made without approval from the release-team. Translation and documentation can continue. |
|
27 |
Mar 29 |
GNOME 2.30.0 newstable tarballs due |
Hard Code Freeze ends, but other freezes remain in effect for the stable branch. |
We accept potential predefined regressions in a11y. We clearly announce these regressions in the release notes. |
Mar 31 |
GNOME 2.30.0 newstable release |
|
|
|
April |
||||
31 |
Apr 26 |
GNOME 2.30.1 newstable tarballs due |
|
|
Apr 28 |
GNOME 2.30.1 newstable release |
|
|