Fossology Release Process (Draft)

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

Announce candidate release (fossology mailing list) : Template needed
Create a tag in svn for the release candidate (e.g. tags/rc/0.6.5_rc1) How To
Check/update INSTALL and INSTALL.multi
Build deb packages
Build rpm packages
Post packages to SourceForge
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

Tag release (svn, remove “rc” label)
- Coordinate with Matt Taggart for creating the final debian changelog entry and building the official debain packages.
- Build debian packages for lenny.
Create initial tarball from svn
Create unofficial debian packages and place on fossology.org.
Upload tarball ~~and release notes~~ to Sourceforge release notes are not provided on sourceforge; users are referred to http://fossology.org/release_notes
Update release notes (Dokuwiki) DONE
- Document upgrade path from previous version(s)upgrading_from_fossology_1.0.0
- Bug owners are responsible for documenting any outstanding bug targeted for the release.
- Update documentation (Dokuwiki, README, etc)
Create RPMs for RHEL4, RHEL5, CentOS4, CentOS5
- post to SourceForge
- add to fossology.org yum repo
Create RPMs for Fedora 11, 12
- post to SourceForge
- add to fossology.org yum repo
Install on public running instance
Install on internal hp instance
Announce release (fossology, fossbazaar) - See sending_email_announcement
Update fossology.org front page
- update development status
- update download page
- update install page (Mary talk to Adria about simplifying these updates)
ensure release packages are externally available from the location referred to by the download page

FOSSology