Release Process¶

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

Release Candidates¶

• 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
• Build Packages
  • All packages are built on fossbuild.usa.hp.com using project builder
• Post tarball and release notes to SourceForge
• Copy packages to fossology.org (see below)
• Create list of known issues
• Announce candidate release to fossology@fossology.org & fossology-devel@fossology.org mailing lists using this (or a similar) template, 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)
• Increment version number in makefile.conf file (svn)
• Update changelog (svn)
• Update schemaspy on fossology.org

Final Release¶

• 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.
• Tag release (svn, remove "rc" label)
• Create initial tarball from svn
• Create unofficial debian packages and place on fossology.org.
• Upload tarball <del>and release notes</del> to Sourceforge. (The "Download Now!" button will be automatically updated to the latest version. Release notes are not provided on sourceforge; users are referred to http://fossology.org/release_notes.)
• Update "Release Notes":release_notes
  • Document upgrade path from previous version(s) on the "Install":install page.
  • Bug owners are responsible for documenting any outstanding bug targeted for the release.
• Update documentation (Dokuwiki, README, etc)
• Create RPMs packages for RHEL and CentOS
  • post to SourceForge
  • <del>add to fossology.org yum repo</del>
• Create RPMs for Fedora
  • post to SourceForge
  • <del>add to fossology.org yum repo</del>
• Install on public running instance fossology.org
• Install on internal hp instance
  • perform db dump first
  • take care not to erase bucket data
• Updates to fossology.org
  • front page
  • update roadmap
  • update download page
  • update install page
• Ensure release packages are externally available from the location referred to by the download page
• Ask for a 2nd quick review of the changes made to fossology.org and the release announcement (Ask bobg, taggart and others on irc #fossology channel)
• Announce release (fossology, fossbazaar) - See how_to_create_a_new_release

Copy Packages to fossology.org¶

• Packages on fossology.org are stored at:/var/www/fossology.org/htdocs/releases/.
• Create a new directory and populate it with Debian Fedora RHEL and Ubuntu directories.
  • Create any needed subdirectories. For example, Debian/squeeze or Fedora/15 use the directory tree on fossbuild (in /var/www/ftp/pub) as a guide.
• You must copy from fossbuild to fossology.org as the user fossology. The folks hosting us have set up a common login called fossology and in some way linked our individual keys to that login.
  • For example, to copy the rc2 Ubuntu bits from fossbuild to fossology.org:
    cd /var/ftp/pub/fossology/2.0.0rc2/ubuntu
scp -r * fossology@fossology.org:/var/www/fossology.org/htdocs/releases/2.0.0-rc2/Ubuntu

NOTE the use of fossology@fossology.org:

You will be asked to supply the key phase for your ssh key that was supplied to the redmine folks.