Release Guide
From NeoWiki
Contents |
[edit] How to do a Neo release
[edit] Preparations
- Verify that you (and maven) are running java 1.5. Maven 2.0.7+ should display both java version and maven version when executing mvn -version
- Make sure that Neo trunk is nice and clean and contains no uncommited stuff (this is important as everything that's in your trunk
may be included in the tag)
- Make sure that trunk/CHANGES.txt has relevant notes on the release
- If Neo trunk depends on a SNAPSHOT of shell you first have to release the new version of the shell and modify the pom to use that release. (TODO: fix shell mvn clean javadoc:javadoc assembly:assembly)
- Execute svn cp trunk tags/yourrelease
- Change to the tag directory and update the version number of the pom (removing -SNAPSHOT)
[edit] Releasing binary and source assemblies
- In the tag directory generate: mvn clean javadoc:javadoc assembly:assembly
- Upload the generated binary and source releases (found under target/) to http://dist.neo4j.org
- Upload CHANGES.txt overwriting the existing change log to http://dist.neo4j.org
- Change links on http://neo4j.org/download
[edit] Releasing javadocs
- Generate: mvn clean javadoc:jar
- Rename current directory to previous-release-version and create a new current folder
- Upload the target/javadoc.jar to http://api.neo4j.org/current folder and unpack it
[edit] Finalizing the release
- Deploy source, binary and javadocs to m2 repository mvn clean deploy
- svn commit in tag dir (should only commit the pom and the tag)
- Go back to trunk, bump the version number in pom to nextrelease-SNAPSHOT and commit
