You are looking at historical revision 24225 of this page. It may differ significantly from its current revision.
CHICKEN release policy
- The CHICKEN core system is maintained in a git repository as described in http://code.call-cc.org where the master branch represents the official development status.
- Bugfixes are normally applied directly to the master branch. Changes that might take longer and or are particularly disruptive may be done on separate branches and merged as soon as the work is considered stable enough to use.
- In more or less regular intervals, the patch-level of the release number will be increased (for example "4.5.0" -> "4.5.1") and a tag identical to the release number will be pushed into "master". Once tagged, a development snapshot is automatically generated and placed in dev-snapshots. Usually, these snapshots and any changes made since the last release or snapshot (whatever is more recent) will be announced on the "chicken-users" mailing list.
- The development snapshot is untested and not guaranteed to work. It is not an official CHICKEN release.
- If enough changes for a regular release have accumulated in the master branch, it is merged into the prerelease branch and from there into the release branch. A tag pushed into the release branch will trigger automatic generation of a release tarball.
- Last-minute fixes to a release and updating the version number can so take place in prerelease without getting disturbed by development in the other, more active branches.
- The release tarballs are kept in the releases directory, and the URL to a release follows a fixed per-release pattern, e.g.:
- The URL http://code.call-cc.org/releases/current always points to the latest official release of CHICKEN.