You are looking at historical revision 19405 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.
- Critical bugfixes are normally applied directly to the master branch, and less critical changes or changes that would be disruptive are made on the experimental branch.
- In more or less regular intervals, changes from the experimental branch are merged into master, bumping the patch-level of the release number (for example "4.5.0" -> "4.5.1") and tagging the repository with a tag identical to the release number. Once tagged, a development snapshot is automatically generated and placed in dev-snapshots,
- 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.