GNOME 2.31.x Development Series
GNOME 2.31.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.31.x series will become the official 2.32 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 git master
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
This webcal schedule link might make subscribing easier.
High risk areas and potential showstoppers for GNOME 3.0:
(Please contribute if you can. Note that this list is not necessarily complete.)
a11y in general: Huge number of risks, mostly because of heavily understaffed team and missing funding. See the GNOME 3 a11y overview page for a complete list. Currently it is likely that some goals will not be achieved.
GTK+/Glib: Continous breakage of apps by adding missing GTK accessor functions and pending sealings
- Python: State of the bindings / pygi
Nice to have (no showstoppers):
Stop using libegg. Probably affected modules according to these stats: anjuta, brasero, deskbar-applet, eog, epiphany, evince, fileroller, gnome-control-center, (gnome-mag), gnome-settings-daemon, hamster-applet, nautilus, seahorse, Tomboy, tracker.
- GDBus to replace dbus-glib
Stop copying EggSMClient code into modules and provide proper session management (also see bug 79285)
Note:
- Only two maintenance releases for 2.30.x, as for 2.28.x - module maintainers are free to create a 2.30.3 tarball
- Two weeks hardcode freeze for 3.0
Numbers like "only X modules depending on foo" refer to these statistics
Comments/Discussion:
Please do not add comments here. Keep any discussion streamlined on desktop-devel mailing list.
|
![/!\](/gnome/gnome-responsive/img/dialog-warning-symbolic.png "/!\"){kind=small}
Release Team announced on July 29th that GNOME 3.0 will be released in March 2011. Week |
Date |
Task |
Notes |
Cleanup targets |
February |
||||
-6 |
Feb 15 |
|
Start of new (app) modules proposal period |
|
March |
||||
0 |
Mar 29 |
GNOME 2.30.0 stable tarballs due |
|
|
Mar 31 |
GNOME 2.30.0 stable release |
|
|
|
April |
||||
4 |
Apr 26 |
GNOME 2.30.1 stable tarballs due |
|
|
Apr 28 |
GNOME 2.30.1 stable release |
|
|
|
May |
||||
5 |
May 03 |
GNOME 2.31.1 unstable tarballs due |
End of new (app) modules proposal period |
0 modules depending on libglade (sound-juicer) |
May 05 |
GNOME 2.31.1 unstable release |
|
|
|
6 |
May 10 |
|
Module Freeze: new modules are chosen now. |
|
8 |
May 24 |
GNOME 2.31.2 unstable tarballs due |
|
a11y: Bonobo-based gnome-speech either replaced by speech-dispatcher or ported to D-Bus |
May 26 |
GNOME 2.31.2 unstable release |
|
|
|
June |
||||
10 |
Jun 07 |
GNOME 2.31.3 unstable tarballs due |
|
Less than 30 modules still using gconf instead of GSettings/dconf |
Jun 09 |
GNOME 2.31.3 unstable release |
|
|
|
12 |
Jun 21 |
GNOME 2.30.2 stable tarballs due |
|
|
Jun 23 |
GNOME 2.30.2 stable release |
|
|
|
13 |
Jun 28 |
GNOME 2.31.4 unstable tarballs due |
|
Less than 20 modules still using gconf instead of GSettings/dconf |
Jun 30 |
GNOME 2.31.4 unstable release |
|
|
|
July |
||||
15 |
Jul 12 |
GNOME 2.31.5 unstable tarballs due |
String Change Announcement Period: All string changes must be announced to both gnome-i18n@ and gnome-doc-list@. |
Less than 10 modules still using gconf instead of GSettings/dconf |
Jul 14 |
GNOME 2.31.5 unstable release |
|
|
|
16 |
Jul 24 |
|
GUADEC 2010 (July 24-30) |
|
August |
||||
18 |
Aug 02 |
GNOME 2.31.6 unstable tarballs due |
Feature Freeze: new functionality is chosen now. |
|
Aug 04 |
GNOME 2.31.6 unstable release |
|
|
|
19 |
Aug 09 |
|
|
|
20 |
Aug 16 |
GNOME 2.31.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@) |
|
Aug 18 |
GNOME 2.31.90 beta release |
|
|
|
22 |
Aug 30 |
GNOME 2.31.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@). |
|
22 |
Sep 01 |
GNOME 2.31.91 beta release |
|
|
24 |
Sep 13 |
GNOME 2.31.92 rc tarballs due |
Hard Code Freeze: no source code changes can be made without approval from the release-team. Translation and documentation can continue. |
|
Sep 15 |
GNOME 2.31.92 rc release |
|
|
|
26 |
Sep 27 |
GNOME 2.32.0 newstable tarballs due |
Hard Code Freeze ends, but other freezes remain in effect for the stable branch. |
|
Sep 29 |
GNOME 2.32.0 newstable release |
|
|
|
October |
||||
30 |
Oct 25 |
GNOME 2.32.1 newstable tarballs due |
|
|
Oct 27 |
GNOME 2.32.1 newstable release |
|
|
|