You are looking at historical revision 9510 of this page. It may differ significantly from its current revision.

Chicken release policy ===
  1. The release tarballs are kept in the releases directory, and the URL to a release follows a fixed per-release pattern, e.g.: <blockquote> <pre> http://chicken.wiki.br/releases/3.4.5/NEWS http://chicken.wiki.br/releases/3.4.5/chicken.pdf http://chicken.wiki.br/releases/3.4.5/chicken-3.4.5.tar.gz http://chicken.wiki.br/releases/3.4.5/chicken-3.4.5-linux-x86.tar.gz http://chicken.wiki.br/releases/3.4.5/chicken-3.4.5-mingw32-x86.tar.gz </pre> </blockquote>
  2. The URL http://chicken.wiki.br/releases/current always points to the latest official release of Chicken.
  3. There is a development snapshot, automatically built and published on dev-snapshots each time the Chicken version number in trunk is increased. The development snapshot is untested and not guaranteed to work. It is not an official Chicken release. If a user wants to build the latest Chicken, but they do not want to do a full SVN checkout, they can fetch the development snapshot tarball and use it for that purpose.
  4. The following cyclic procedure will be followed to make new releases:
    1. current version of Chicken is 3.5.0 (for example)
    2. a developer adds some minor library functions to Chicken
    3. a release manager sees the new changes, and increases the number in trunk/version.scm to 3.5.1
    4. the version increase triggers the development snapshot script to build a new tarball for 3.5.1, which is published on the development snapshot page
    5. this process continues, until the release manager deems that sufficient number of changes and fixes have been made in trunk, increases the version number to 3.6.0, and merges with the prerelease branch
    6. some testing is done on the prerelease branch (salmonella, unit tests, etc)
    7. once the prerelease branch is deemed stable, the release manager makes an official tarball release and puts it on the release page