Release Procedure

prior to release

1. run valgrind with all unit tests against GCC/Clang
2. ensure that all documentation packages are up to date with any API/build changes
   • doxygen
   • javadoc
   • docs in C#
   • opendnp3 guide
3. Ensure that GCC/Clang build with "-Wall -Werror" for x32 and x64 builds
4. Check that the Nuget API key for Appveyor is still valid (expires every year)

performing the release

1. Update version numbers in CMake. The .NET bindings automatically use this version number as well.

2. Update version number in config/doxygen.config.

3. Update the Changelog.

4. Run the maven release plugin to update the versions in POMs and create the tags

cd java
mvn release:prepare

Add the release version and new development (snapshot) version when prompted.

This will create two commits (one w/ release versions in POMs and another following it with the snapshot versions). It will also create a tag, e.g. "2.3.0".

5. If all seems right:

git push origin master --tags

6. Generate doxygen doxygen config/doxygen.config and publish it if this is a major release with any changes to the public API.

7. Mark the new tag as a release via Github so users see it as such.