7 Preparing Releases
Steps to release a new version of PPW:
- Double-check version number in configure.ac, and any other places
that include that version number. Usually just running the
update-versions.pl script that gets generated by autoconf right
before doing a
make dist should do the trick.
- Update docs (especially user manual) to reflect any changes or feature
enhancements
- Update NEWS file to show changes and release date
- Make new tag in tags directory (server-side svn cp) of the form RELEASE_X_Y
- Create UNIX source distribution by doing
make distcheck. Be sure
to do an ant dist in javasrc first to update the jar files
that are distributed with the tarball. Also, be sure to do a
make gen in the docs directory to update all generated
documentation like man pages, etc.
Note that typing make release might do some of the above steps
for you automatically, aside from updating the NEWS file and making the
svn tags.
- Create new Java webstart, windows, and OSX versions of GUI (see
javasrc/deploy).
- Test all source tarballs and binaries above on as many platforms as
feasible
- Update website with
- New downloads
- New Java web start version in the site/jws directory
- Appropriate files in the site/vX.Y/sampledata directory
- New HTML versions of the user manual that you obtained from the
make gen command above.
- Update the docs/ppw-devguide.texi file for any new additions
to the release process
- Send email announcements out, including to ppw AT hcs DOT ufl DOT edu