Release Schedule
Contents
Release Schedule for 2.4.x releases
We don't have an actual schedule. We only know we plan for a stable 2.2.x release every 3-6 weeks in order to make available the bugfixes and translation updates.
Actual (past) 2.4.x Schedule:
Version | Date | Wiki | Purpose |
---|---|---|---|
2.4.4 | 2011-03-13 | - | Bugfixes ("very slow startup on windows" bug fixed), Translations |
2.4.3 | 2011-02-26 | - | Bugfixes (SQL on Windows working again), Translations |
2.4.2 | 2011-02-06 | - | Bugfixes, Translations (SQL on windows was broken here) |
2.4.1 | 2011-02-05 | - | Bugfixes, Translations (Release was broken, quickly replaced by 2.4.2) |
2.4.0 | 2010-12-21 | - | - |
Release Schedule for 2.3.x
This is a draft release schedule for unstable 2.3.x releases of gnucash, which will eventually lead to the stable 2.4.0 release of gnucash with new features.
Schedule
Actual 2.3.x Schedule:
Version | Date | Wiki | Purpose |
---|---|---|---|
2.3.0 | May 16, 2009 | Announcement 2.3.0 | Initial announcement and call for testers |
2.3.1 | June 7, 2009 | - | Bug fixes |
2.3.2 | July 6, 2009 | - | Bug fixes, translation updates |
2.3.3 | July 23, 2009 | - | Bug fixes, more translation updates, native OSX support |
2.3.4 | August 19, 2009 | - | Bug Fixes, database schema change for DBI backends, more translation updates |
2.3.5 | August 29, 2009 | - | Bug Fixes |
2.3.6 | September 29, 2009 | - | Bug Fixes |
2.3.7 | October 6, 2009 | - | Bug Fixes, revert crash regression on MS Windows |
2.3.8 | December 8, 2009 | - | Bug Fixes |
2.3.9 | February 15, 2010 | - | Bug Fixes & translation updates; revert to GtkHTML for MS Windows, various minor improvements |
2.3.10 | February 18, 2010 | - | Revert crash regression on MS Windows |
2.3.11 | March 19, 2010 | - | Bug Fixes |
2.3.12 | April 21, 2010 | - | String Freeze |
2.3.13 | June 2, 2010 | - | Bug Fixes, fix font and webkit issues on Windows |
2.3.14 | June 8, 2010 | - | bug fixes, fix crash issue on Windows |
2.3.15 | August 20, 2010 | - | bugfixes, again string freeze, probably code freeze |
2.3.16 | Sometime September? | - | Release Candidate |
2.4.0 | December 2010 | Announcement 2.4.0 | Keep in mind that the (Unix) source package and the MS Windows and OSX binaries have to be ready by that date. PR planning |
Release Schedule for 2.2.x
We don't have an actual schedule yet. We only know we plan for a stable 2.2.x release every 3-6 weeks in order to make available the bugfixes and translation updates.
Proposed Schedule:
Release Schedule for 2.1.x
This is a draft release schedule for unstable 2.1.x releases of gnucash, which will eventually lead to the stable 2.2.0 release of gnucash with new features.
Goal
Goal for 2.2.0: Now that the gnome2 port is working well, we are introducing some new features. These are
- ?
- Scheduled Transactions re-work.
- Port to Windows available
Purpose of all 2.1.x releases: Any 2.1.x is not yet stable, but is meant to provide easier access to the current source code for wider testing. Also, at some point in time the 2.1.x series should go into a string freeze so that translators can fully concentrate on their translation work.
PR_planning page
Requirements of 2.1.x releases
- Any 2.1.x has to offer full backward-compatibility of the data file. It should always be possible to use a 2.1.x-saved XML datafile again with any 2.0.x version. This is achieved by the "allow_file_incompatibility" gconf key as introduced in r15612, explained also here.
- Bugzilla queries for the list of bugs assigned to those milestones:
- Open Bugzilla items with 2.1.0 milestone (including resolved)
- Open Bugzilla items with 2.1.1 milestone (including resolved)
- Open Bugzilla items with 2.1.2 milestone (including resolved)
- Open Bugzilla items with 2.1.3 milestone (including resolved)
- Open Bugzilla items with 2.1.4 milestone (including resolved)
- Open Bugzilla items with 2.1.5 milestone (including resolved)
- Open Bugzilla items with 2.2.0 milestone (including resolved)
Caveats
Caveats for testers:
- Any 2.1.x version might crash unexpectedly at any point during runtime. If you test some serious work in a 2.1.x release, make sure you hit "Save" after ever non-trivial workstep.
- The documentation has had screenshots updated, however, most help texts usually only refers to the 2.0.x or even 1.8.x series. Everyone is invited to help improve the documentation; see Development on how to get involved.
Schedule
Actual release dates
- 2.1.0 April 14th; Announcement 2.1.0; Initial announcement and call for testers
- Bug Day April 21st
- 2.1.1 April 28th; Announcement 2.1.1; bugfixing;
- Bug Day May 5th
- 2.1.2 May 19th; Announcement 2.1.2; bugfixing; String Freeze; translation updates
- 2.1.3 June 2; Announcement 2.1.3; critical bugs and more translation updates
- 2.1.4 June 16; Announcement 2.1.4; Release Candidate One i.e. final bugfixes (esp. windows), final translation updates. We need the next 2 weeks for PR planning, and we need qualified feedback whether this release works fine for Windows users
- 2.1.5 July 2; Announcement 2.1.5; Release Candidate Two i.e. final bugfixes (esp. windows), final translation updates.
- 2.2.0 July 15; Announcement 2.2.0; Keep in mind that the (Unix) source package and the Windows binary have to be ready by that date. PR planning
All dates are the Saturday of a weekend. It is proposed to have a release every other week or in three week intervals.
Release Schedule for 2.0.x
Actual release dates:
- 2.0.5 February 18th, 2007; Announcement 2.0.5; All Bugzilla items with 2.0.5 milestone including resolved
- 2.0.4 January 1st, 2007; Announcement 2.0.4; All Bugzilla items with 2.0.4 milestone including resolved
- 2.0.3 December 10th, 2006; Announcement 2.0.3; All Bugzilla items with 2.0.3 milestone including resolved
- (important bugfix: crash on quit during save, bug 353450)
- 2.0.2 October 8th, 2006; Announcement 2.0.2; All Bugzilla items with 2.0.2 milestone including resolved
- 2.0.1 July 30th, 2006; Announcement 2.0.1; All Bugzilla items with 2.0.1 milestone including resolved
- 2.0.0 July 09th, 2006; Announcement 2.0.0; All Bugzilla items with 2.0.0 milestone including resolved