Recent Changes - Search:

WikiDoc

Categories

Current development schedule

Development.CurrentDevelopmentSchedule History

Hide minor edits - Show changes to markup

January 23, 2006, at 02:31 PM by 212.180.15.164 -
Changed lines 25-27 from:

Proposed Development Schedule

to:

Proposed Development Schedule

Changed lines 86-87 from:

Alpha8/X "Debug" binaries

to:

Alpha8/X "Debug" binaries

Changed lines 100-101 from:

cbu 12dec03]] cbu 29apr04

to:

cbu 12dec03 - cbu 29apr04

January 23, 2006, at 02:30 PM by 212.180.15.164 -
Added lines 1-103:

(:title Current development schedule:)

Alpha8/X 8.0b14 was released on 9 December 2003 with a 270 day expiry.

This means that around 20 August 2004 users will see an alert dialog when they launch the application stating that it will expire in XX days, and they will betold to go to the AlphaTcl Wiki home page for a new release.

Sometime around 5 September 2004 the application will fail to launch unless there is a "secret handshake" file present named Don't expire Alpha beta (exactly).

The first time that the alert dialog appears, the new release should have already been tested, uploaded, and announced to the various listservs, and posted on VersionTracker et al as well. This suggests that the new release should be made available around 1 August 2004, and that members of the AlphaCabal as well as the AlphaTcl Development Team should create and respect some form of the following development schedule.

As of this writing, the schedule below is simply a proposal. When it is formally adopted, this comment should be removed and some statement regarding is acceptance should be inserted in its place.


Proposed Development Schedule

  • 10 December 2003 - 31 March 2004

Continued development of AlphaTcl, paying particular attention to any bugs filed in AlphaBugzilla? that have relevant target milestones. (See also Development.FinalReleaseIssues)

  • 1 April 2004

Declare a temporary code freeze.

  • 1 April - 15 April 2004

Only true bug fixes or updates to documentation will be allowed.

  • 16 April 2004

Tag AlphaTcl as CURRENT, and encourage all beta-testers (including those on the Users list as well as the Developers) to update from the CVS.AlphaTclCVS in order to test the latest changes.

  • 16 April - 31 May 2004

Unfreeze AlphaTcl.

Continued development of AlphaTcl, paying particular attention to any bugs filed in AlphaBugzilla? that have relevant target milestones. (See also Development.FinalReleaseIssues)

  • 1 June 2004

Declare a code freeze, to remain in effect until 8.0b16 has been released.

  • 1 June - 31 June 2004

Only true bug fixes or updates to documentation will be allowed.

  • 1 July 2004

Tag AlphaTcl as CURRENT, and create a 8.0b15fc1 final release candidate.

Upload this to some server that won't be detected by VersionTracker.

Announce the final candidate to all listservs.

  • 1 July - 31 July 2004

AlphaTcl code freeze remains in effect, only true bug fixes or updates to documentation will be allowed.

Release additional 8.0b15fc binaries as needed to deal with remaining core issues.

  • 1 August 2004

Target release date for 8.0b16 (or possibly 8.0 final).


Alpha8/X "Debug" binaries

During the development cycle, Bernard has been in the habit of compiling and posting various "Debug" binaries so that developers and users can test recent changes. (Thanks!) These are generally announced on one of the AlphaTclMailingLists. He has been giving this unique version numbers of the form

 
    8.0b15-D7
    8.0b15-D10

Rather than add all of these to the AlphaBugzilla? "version" field options, we simply have "8.0b15". The "Help > Report A Bug" menu item automatically strips these "-D7" strings from the current version number so that Bugzilla won't reject these reports.


cbu 12dec03]] cbu 29apr04

Category.Development

Page last modified on January 23, 2006, at 02:31 PM
Hosted on SourceForge.net Logo