The following steps should be taken to produce new FOSSology releases:

• Determine the revision number and create a tag in svn for the release candidate (e.g. tags/rc/0.6.5_rc1): How to Create a New Release
• Check/update INSTALL and INSTALL.multi
• Update changelog (svn) what does this mean?
• Build Packages
  • All packages are built on fobuild.usa.hp.com using project builder
• Post How_to_Create_a_New_Release#Creating-a-tarball from fossbuild:/home/build/pb/projects/fossology/delivery
• Post release notes to SourceForge from Release_Notes
• Copy packages to fossology.org (see below)
• Create list of known issues from the issue tracker
• Announce candidate release to [email protected] & [email protected] mailing lists using this (or a similar) RC_email_announce, including the list of supported platforms and known issues
• External & internal testing cycles with release candidate
  • Install on single test system (internal)
  • Initial sanity tests (internal)
  • Install on multiple test system (internal)
  • Multiple system/integration tests (internal)
  • Perform upgrade tests (from previous release)
• Updates to fossology.org
  • Add a new News item
  • Wiki#Download-38-Install-FOSSology
  • Add a new Install and Update page (similar to these: Install_1_4_0, Install_2_0)

• Begin a discussion on irc and send email to fossology-devel that the final release process is taking place (suggested by taggart, so we don't miss stuff). Give people a few days to respond and review the release notes that will be sent with the release announcement.
• Complete/double-check the list of items above for Release Candidates

• Login to fossology.org from fobuild as user fossology ([laser@fobuild ~]$ssh [email protected]) Your public key must be added to the authorized_keys file (for the fossology user).
• Packages on fossology.org are stored at:/var/www/fossology.org/htdocs/releases/.
• Create a new version directory Eg. /var/www/fossology.org/htdocs/releases/2.1.0
• Create the subdirectories using the directory tree on fobuild (in /var/www/ftp/pub) as a guide. For example:

fossology@fossology:/var/www/fossology.org/htdocs/releases$ for i in Debian Fedora RHEL Ubuntu; do mkdir -p 2.1.0/$i; done

• You must copy from fossbuild to fossology.org as the user fossology. Your public key must be added to the authorized_keys file (for the fossology user) to copy the files. ** For example, to copy the rc2 Ubuntu bits from fossbuild to fossology.org:

cd /var/ftp/pub/fossology/2.0.0rc2/ubuntu scp -r * [email protected]:/var/www/fossology.org/htdocs/releases/2.0.0-rc2/Ubuntu

NOTE the use of [email protected]: scp -r * [email protected]:/var/www/fossology.org/htdocs/releases//Debian/ scp -r * [email protected]:/var/www/fossology.org/htdocs/releases//Fedora/ scp -r * [email protected]:/var/www/fossology.org/htdocs/releases//RHEL/ scp -r * [email protected]:/var/www/fossology.org/htdocs/releases//Ubuntu/