Difference between revisions of "Release Schedule"
m (→Schedule: delete obsolete proposal) |
(→Schedule: jsled's proposal with additional 2.1.5 rc2) |
||
Line 38: | Line 38: | ||
* 2.1.3 June 2; [[Announcement 2.1.3]]; critical bugs and more 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.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.2.0 | + | * 2.1.5 June 30; [[Announcement 2.1.5]]; '''Release Candidate Two''' i.e. final bugfixes (esp. windows), final translation updates. |
− | ::How about this: Source package is tagged in SVN and uploaded on Saturday, | + | * 2.2.0 July 14..17; [[Announcement 2.2.0]]; Keep in mind that the (Unix) source package ''and the Windows binary'' have to be ready by that date. (I prefer to have the binary and announcement on a Tuesday - Nathan) |
+ | ::How about this: Source package is tagged in SVN and uploaded on Saturday, July 16th. Binary package is created and uploaded by Monday, July 16th (and needs to be copied to gnucash.org as well). Announcement is sent out on Tuesday, July 17th. Would that work? --[[User:Cstim|Cstim]] 04:59, 25 June 2007 (EDT) | ||
All dates are the Saturday of a weekend. It is proposed to have a release every other week or in three week intervals. | All dates are the Saturday of a weekend. It is proposed to have a release every other week or in three week intervals. |
Revision as of 08:59, 25 June 2007
Contents
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.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
Proposed schedule:
- 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 June 30; Announcement 2.1.5; Release Candidate Two i.e. final bugfixes (esp. windows), final translation updates.
- 2.2.0 July 14..17; Announcement 2.2.0; Keep in mind that the (Unix) source package and the Windows binary have to be ready by that date. (I prefer to have the binary and announcement on a Tuesday - Nathan)
- How about this: Source package is tagged in SVN and uploaded on Saturday, July 16th. Binary package is created and uploaded by Monday, July 16th (and needs to be copied to gnucash.org as well). Announcement is sent out on Tuesday, July 17th. Would that work? --Cstim 04:59, 25 June 2007 (EDT)
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
Release Schedule for 1.9.x
This is a draft release schedule for unstable 1.9.x releases of gnucash, which will eventually lead to the stable 2.0.0 release of gnome2-based gnucash.
Goal
Goal for 2.0.0: For the first 2.0.0 release the plan is to finish porting those parts of gnucash that have already been started (i.e. new windowing system, account tree, commodities tree, etc.), but not to port any additional features unless absolutely required.
Purpose of all 1.9.x releases: Any 1.9.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 1.9.x series should go into a string freeze so that translators can fully concentrate on their translation work.
Requirements of 1.9.x releases
- Any 1.9.x has to offer full backward-compatibility of the data file. It should always be possible to use a 1.9.x-saved XML datafile again with any 1.8.x version. (Note: Actually we restrict this backward compatibility to >= 1.8.5 because we are using the correct XML namespace definitions in the file; capabilities for reading those were added in 1.8.5, 17 Aug 2003)
- Bugzilla queries for the list of bugs assigned to those milestones:
- All Bugzilla items with 1.9.0 milestone including resolved
- All Bugzilla items with 1.9.1 milestone including resolved
- All Bugzilla items with 1.9.2 milestone including resolved
- All Bugzilla items with 1.9.3 milestone including resolved
- All Bugzilla items with 1.9.4 milestone including resolved
- All Bugzilla items with 1.9.5 milestone including resolved
- All Bugzilla items with 1.9.6 milestone including resolved
- All Bugzilla items with 1.9.7 milestone including resolved
- All Bugzilla items with 1.9.8 milestone including resolved
- Open Bugzilla items with 2.0.0 milestone (including resolved)
Caveats
Caveats for testers:
- Any 1.9.x version might crash unexpectedly at any point during runtime. If you test some serious work in a 1.9.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 1.8.x series. Everyone is invited to help improve the documentation; see Development on how to get involved.
Schedule
Actual release dates:
- 1.9.0 February 8th; Announcement 1.9.0, Initial announcement and call for adventurous testers
- 1.9.1 February 19th; Announcement 1.9.1; bugfixes
- 1.9.2 March 5th; Announcement 1.9.2; bugfixes
- 1.9.3 March 19th; Announcement 1.9.3; bugfixes
- 1.9.4 April 5th; Announcement 1.9.4; "soft" string freeze; bugfixes; call for translations; call for more testers
- 1.9.5 April 16th; Announcement 1.9.5; bugfixes; start of String Freeze.
- 1.9.6 May 14th; Announcement 1.9.6; bugfixes; still String Freeze; first "beta" release
- 1.9.7 June 5th; Announcement 1.9.7; bugfixes; second "beta" release
- 1.9.8 June 18th; Announcement 1.9.8; release candidate! Yeah!
- 2.0.0 July 09th; Announcement 2.0.0
Proposed future schedule. All dates are the Sunday of a weekend. It is proposed to have a release every other week or in three week intervals.
The tarball is prepared ("make dist") and copied on the ftp server by Chris Lyttle.