Making a CLAM Release Public

Create the tarball

Login to mtg150.upf.es as user admin150, and go to the scripts directory:

cd ~/tarballs/scripts/

Edit the run.sh script, moving the line to generate the new CLAM release to the top (and probably adding a call to exit() below)

Run the script:

./run.sh

Upload the tarball

Check the generated tarballs/zips and upload them to the webserver

cd ~/tarballs/out/
scp CLAM-VERSION.tar.gz clamadm@www.iua.upf.es
scp CLAM-VERSION.zip clamadm@www.iua.upf.es

Editing the webpages

Here we describe how to edit the webpages directly on the server, but since these files are in CVS, you can also checkout the module CLAM-web, edit it locally, and do a

cvs update

on the server. If you edit the files directly and the server, don't forget to do a

cvs commit

afterwards.

Update the download page

Login to www.iua.upf.es as user clamadm, and edit the download-in.html file, moving the previous stable version to the old stable versions section, and add the entries for the new stable version.

Run the script to generate download.html:

perl generate-download.pl

Update the changelog page

Extract the ChangeLog.txt from the uploaded tarball:

tar zxOf CLAM-0.5.4.tar.gz CLAM-0.5.4/ChangeLog.txt > ChangeLog.txt

And generate the ChangeLog.html file:

./changelog2html.py ChangeLog.txt > ChangeLog.html

Update the doxygen documentation

The CLAM web page includes two Doxygen documentation trees. One is automatically extracted from the development branch and the other one must be manually extracted from the main branch whenever a public release is done. The CLAM CVS module contains a script (test/GenerateDoxygen.sh) that you can execute in order to generate it.

test/GenerateDoxygen.sh main

You should provide several times the password for the clamadm user. The script is not very mature so take some time to check that it is working properly.

Update the main page

Add a news item about the new release to the file main.html