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	When the software is ready to be released it is rolled into a source distribution tarball. The 'make dist' target makes sure this is a clean tarball without any files that are strictly for development and not for distribution. 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	make a tarball record the sha1 and sha256 checksums upload to software.nikhef.nl write a signed e-mail to grid-mw-security@nikhef.nl with the name of the tarball and the checksums
Packaging	RPM Deb spec files, mock, koji debian/ directory, cowpoke
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.