Page History

Make sure the #One time setup steps have been performed

If releasing from the trunk, first make a branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more distruptive advances in the trunk from potentially causing problems with the release. A branch can be made by running:

Update the POMs to remove "-SNAPSHOT" from the version. If you have perl installed, you can easily do it with a single command:

Commit the POM changes

Perform the build with documentation and install it in the local repository (this step is required because there is a bug in Maven's javadoc generation aggregated between multiple modules):

Verify the signatures:

Now actually build the javadocs and perform the deploy upload:

Tag the branch with the release number:

Update the pom.xml files to the subsequent version with the -SNAPSHOT suffix:

Commit the POM changes

Start a vote for the release on the open-jpa-dev@incubator.apache.org mailing list. For an example of the mail, see this archived vote

If the vote is successful after 3 days, mail general@incubator.apache.org starting a vote for authorization to release

Once that vote is successful, update the http://cwiki.apache.org/openjpa/downloads.html page with information about the download

The documentation links at http://cwiki.apache.org/openjpa/documentation.html also needs to be updated. You can do this by checking out a copy of the OpenJPA static site documents into a scratch directory, unpacking the OpenJPA binary into the docs section, adding the new docs, and then committing and updating the docs on the server-side:

The static site will take a little while to synchronize, but eventually you should see the new documentation version at http://incubator.apache.org/openjpa/docs/. Once you see that, add a link to the new documentation release at http://cwiki.apache.org/openjpa/documentation.html