Cheat Sheet
The following table gives an overview of the workflow and procedures involving development and delivery of our software.
|
|
resources
|
procedures
|
| Source
|
|
- 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
|
|
| Packaging
|
RPM
|
- 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
|
Generating RPM packages
|
| Debian
|
|
|
Generating Debian packages
|
| Distribution
|
- mwsec repository
- EMI, IGE, UMD and other middleware integrators
- Fedora, EPEL, Debian, Ubuntu
|
koji tags, sigul, mash, signed repositories, dput
|
| RPM
|
| resources for RPM distribution
|
procedures for RPM distribution
|
| Debian
|
| resources for Debian distribution
|
procedures for Debian distribution
|
