1 ## Notes about release process ##
3 The different binary packages are built by a group of volunteers called the release-team.<br/>
4 The packages themselves are stored under /afs/grand.central.org/software/openafs/*release-number*.<br/>
6 The distibution-page on www.openafs.org is created automatically by the script *make_www_release*<br/>
7 found in the *tools* (git://git.openafs.org/tools.git) repository.
9 Thus, the packagers are asked to provide the packagers in a certain directory structure so that <br/>
10 this html-page is constructed correctly:
12 **OS**/**arch**/*package-files*
14 where **OS** has to match to the regex :
15 $prefix=~s/^(.*?)[-\d]+.*/$1/;
17 and $prefix should be then one of :
22 'dux' => 'Digital UNIX',
24 'freebsd' => 'Free BSD',
29 'openbsd' => 'Open BSD',
30 'opensuse'=> 'OpenSUSE',
31 'redhat' => 'RedHat Linux',
32 'rhel' => 'RedHat Enterprise Linux',
33 'solaris' => 'Oracle Solaris',
34 'sle' => 'SUSE Linux Enterprise',
35 'winnt' => 'Windows 2000/XP/2003',
36 'win9x' => 'Windows 95/98/Millenium Edition',
39 and **arch** is free-form and typically one of i386,i586,i686,x86_64
41 some example directory would then be:
48 if there is a source package available (like a source-rpm), it should be put directly under the **OS** directory.