GNOME 2.7.x is an unstable development series intended for testing and hacking purposes. Like the Linux kernel, GNOME uses odd minor version numbers to indicate development status, so this unstable 2.7.x series will eventually become the official 2.8 stable release.
Suites & Module ListsFor more information about each suite of software in this release, including a list of proposed and final modules, see: |
Release TeamSee the Release Planning page for more information about the GNOME Release Team and process. If you need help, email the Release Team (release-team at gnome.org). Subscribe to devel-announce-list for release-team and other developer-related announcements. |
Testing and BugsSet up a safe testing platform following Andrew Sobala's Testing Guide, and join the GNOME Bugsquad's weekly Bug Days. Check the 2.7 Bugs Report for things to fix! :-) |
Subscribe to our totally elite webcal schedule! Do it! DO IT NOW! (Also available via http).
| Week | Date | Task | Big Picture |
|---|---|---|---|
| April 2004 | |||
| 1 | April 5th | ||
| 2 | April 12th | ||
| 3 | April 19th | 2.6.1 tarballs due | First 2.6.x maintenance release - translations, plus bug and performance fixes. |
| April 21st | 2.6.1 release | ||
| 4 | April 26th | ||
| May 2004 | |||
| 5 | May 3rd | ||
| 6 | May 10th | ||
| 7 | May 17th | 2.7.1 tarballs due | First 2.7.x release! Go wild. Maintainers who wish to propose their modules for inclusion should speak up now. :-) |
| May 19th | 2.7.1 release | ||
| 8 | May 24th | ||
| 9 | May 31st | ||
| June 2004 | |||
| 10 | June 7th | 2.7.2 tarballs due | |
| June 9th | 2.7.2 release | ||
| 11 | June 14th | 2.6.2 tarballs due | Second and potentially final 2.6.x maintenance release - translations, plus bug and performance fixes. |
| June 16th | 2.6.2 release | ||
| 12 | June 21st | ||
| 13 | June 28th | 2.7.3 tarballs due | |
| June 30th | 2.7.3 release | ||
| July 2004 | |||
| 14 | July 5th | ||
| 15 | July 12th | ||
| 16 | July 19th | 2.7.4 tarballs due |
API/ABI Freeze: developer APIs should be frozen at this point. Feature and Module Freeze: new modules and functionality are chosen now. String Change Announcement Period: All string changes must be announced to gnome-i18n@. |
| July 21st | 2.7.4 release | ||
| 17 | July 26th | ||
| August 2004 | |||
| 18 | August 2nd | 2.8.0 Beta 1 (2.7.90) tarballs due | UI Freeze: No UI changes may be made without approval from the release-team. |
| August 4th | 2.8.0 Beta 1 (2.7.90) release | ||
| 19 | August 9th | ||
| 20 | August 16th | 2.8.0 Beta 2 (2.7.91) tarballs due | String Freeze: no string changes may be made without confirmation from the l10n team (gnome-i18n@) and notification to release team. |
| August 18th | 2.8.0 Beta 2 (2.7.91) release | ||
| 21 | August 23rd | ||
| 22 | August 30th | 2.8.0 Release Candidate 1 (2.7.92) tarballs due | Hard Code Freeze: no source code changes can be made without approval from the release-team. Translation and documentation can continue. |
| September 2004 | |||
| September 1st | 2.8.0 Release Candidate 1 (2.7.92) release | ||
| 23 | September 6th | ||
| 24 | September 13th | 2.8.0 tarballs due | |
| September 15th | September 15th: 2.8.0 release! | Hard Code Freeze ends, but other freezes remain in effect for the stable branch. | |
Reminder: When you create a stable branch, be sure to remember to let release-team, desktop-devel-list, gnome-doc-list, and gnome-i18n know. This is especially important if you branch before the stable release. An email also needs to be sent if you decide to use an older stable branch for this release as well.
See this page if you would like to get involved.