swIMP Developer's page

hosted at

Content

Procedure for check-in into version control

When checking out the repository for the first time, please execute the following steps:

• Run ./prepareGnuBuild.sh before running the usual ./configure ; make

Procedure for check-in into version control

When producing a new release the following steps have to be executed:

• Run make distclean in order to remove superfluous files.
• Run cvs update and check for files to be added or removed from version control (or to be added to .cvsignore). Make sure to also add .cvsignore to version control.
• When cvs update does not return any more unknown files, you are ready to execute cvs ci. Please add a meaningful check-in comment.

Release procedure

When producing a new release the following steps have to be executed:

• Update the version number in AC_INIT macro in configure.in.
• Update the version information for the libraries in iface/Makefile.am.

The corresponding positions in the source files are marked with 'XXX_RELEASE'

• Set clean environment by . swimpEnv.sh -c,
• Execute make distclean followed by configure, make and make check and correct any errors that might show up.
• Execute make testjar to check the jar for completeness.
• Execute make javadoc to update documentation.
• Execute make distcheck and correct any errors that might show up.
• Execute make dist to generate the tarball.
• Inspect the contents of the tarball.
• Execute make bindist to create the binary distribution.
• Execute make bindist-check to test the binary distribution.
• Update the project web-pages (Are the versions of the libraries and tools up-to-date?).
• Inspect the contents of the tarball of the binary distribution.
• Update ChangeLog.
• Unpack tarball and perform test installation (first without then with make forcegen).
• Check-in version into version control.
• Rerun make distcheck and use this tarball for the official release.