User:Dennisvd@nikhef.nl/SoftwareOverview

Cheat Sheet

The following table gives an overview of the workflow and procedures involving development and delivery of our software.

	resources	procedures
Source	the software is maintained in a Subversion repository. Access to SVN is configured in the central LDAP database. The software packages follow the GNU coding guidelines, and use automake/autoconf.	Before tagging, go through the mandatory checklist: Update configure.ac with the right version make distcheck Update the files BUGS, INSTALL, NEWS, README svn update ; svn log -v > ChangeLog commit to SVN Prior to preparing a release, the software should be tagged.
Release	Releasing the tarball requires interaction with several testbed machines. Make good use of the fact that they share the home directories. svn export svn+ssh://svn@ndpfsvn.nikhef.nl/repos/mwsec/tags/component/tag component_tag Run bootstrap on fc17.testbed, to use the newest possible automake/autoconf Run 'make dist' on mwsecbuild.testbed; this machine has all the required dependencies for a build	make a tarball record the sha1 and sha256 checksums upload to software.nikhef.nl write a signed e-mail with the name of the tarball and the checksums
Packaging	RPM Debian SPEC files are maintained in SVN a SPEC file together with the source tarballs can be rolled into a source RPM a source RPM can be rebuild with mock in a controlled environment our koji instance automatically triggers builds on commits The debian directories are maintained separately from their components in SVN. svn-buildpackage will merge the directory with the source tarball. See SAC_Debian_packaging.
Distribution	mwsec repository EMI, IGE, UMD and other middleware integrators Fedora, EPEL, Debian, Ubuntu	koji tags, sigul, mash, signed repositories, dput write Release notes and announce on the announce mailing list.