Difference between revisions of "Release Schedule"
(bugzilla 2.1.5) |
(→Schedule: propose yet another schedule for mid-July) |
||
Line 41: | Line 41: | ||
* 2.1.5 June 30; [[Announcement 2.1.5]]; '''Release Candidate Two''' i.e. final bugfixes (esp. windows), final translation updates. | * 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. | * 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. | ||
− | + | ** How about this: Source package is tagged in SVN and uploaded on Saturday, July 14th. 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) | |
+ | ** Alternatively, if the announcement should be sent out on a Sunday, here's how we could schedule this: Source package is tagged in SVN and uploaded on Thursday, July 12th. Binary package is created and uploaded by Saturday, July 14th (and needs to be copied to gnucash.org as well). Announcement is sent out on Sunday, July 15th. --[[User:Cstim|Cstim]] 03:56, 27 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 07:56, 27 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.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
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.
- How about this: Source package is tagged in SVN and uploaded on Saturday, July 14th. 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)
- Alternatively, if the announcement should be sent out on a Sunday, here's how we could schedule this: Source package is tagged in SVN and uploaded on Thursday, July 12th. Binary package is created and uploaded by Saturday, July 14th (and needs to be copied to gnucash.org as well). Announcement is sent out on Sunday, July 15th. --Cstim 03:56, 27 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