source: project/wiki/release-policy @ 12863

Last change on this file since 12863 was 9510, checked in by Ivan Raikov, 12 years ago

Some more detailed information about the releases directory structure.

File size: 1.8 KB
Line 
1
2=== Chicken release policy ===
3
4# The release tarballs are kept in the [[releases]] directory, and
5the URL to a release follows a fixed per-release pattern, e.g.:
6<blockquote>
7<pre>
8http://chicken.wiki.br/releases/3.4.5/NEWS
9http://chicken.wiki.br/releases/3.4.5/chicken.pdf
10http://chicken.wiki.br/releases/3.4.5/chicken-3.4.5.tar.gz
11http://chicken.wiki.br/releases/3.4.5/chicken-3.4.5-linux-x86.tar.gz
12http://chicken.wiki.br/releases/3.4.5/chicken-3.4.5-mingw32-x86.tar.gz
13</pre>
14</blockquote>
15# The URL [[http://chicken.wiki.br/releases/current]] always points to
16the latest official release of Chicken.
17# There is a development snapshot, automatically built and published
18on [[dev-snapshots]] each time the Chicken version number in trunk is
19increased. The development snapshot is untested and not guaranteed to
20work. It is not an official Chicken release. If a user wants to build
21the latest Chicken, but they do not want to do a full SVN checkout,
22they can fetch the development snapshot tarball and use it for that
23purpose.
24# The following cyclic procedure will be followed to make new releases:
25## current version of Chicken is 3.5.0 (for example)
26## a developer adds some minor library functions to Chicken
27## a release manager sees the new changes, and increases the number
28in trunk/version.scm to 3.5.1
29## the version increase triggers the development snapshot script to
30build a new tarball for 3.5.1, which is published on the development
31snapshot page
32## this process continues, until the release manager deems that
33sufficient number of changes and fixes have been made in trunk,
34increases the version number to 3.6.0, and merges with the prerelease
35branch
36## some testing is done on the prerelease branch (salmonella, unit
37tests, etc)
38## once the prerelease branch is deemed stable, the release manager
39makes an official tarball release and puts it on the release page
40 
41
Note: See TracBrowser for help on using the repository browser.