This will show you how to build and release the ApacheDS subproject. Keep an eye out for warning and note sections that show version specific differences in this process.
Some things have not yet been automated with maven and require users to manually edit some files. Below are the steps to follow.
Edit the apacheds.sh/bat files in the service project directory to update the revision numbers used in that file to reference non-SNAPSHOT releases.
Since we are using Nexus for releases the release process is as follows (see also http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven).
Replace the version by the new version. Be careful, and remove the 'apacheds-parent-' which is proposed for the new tag. We should just use the version number.
This is useful to verify your settings in ~/.m2/settings.xml (Nexus password and GPG key)
This creates a tag here: http://svn.apache.org/viewvc/directory/apacheds/tags/
This deploys the release to a staging repository. Go to https://repository.apache.org/index.html#stagingRepositories and close the staging repository.
This creates and deploys the site via ssh to people.apache.org/www/directory.apache.org/apacheds/gen-docs.
Edit the people.apache.org/www/directory.apache.org/apacheds/gen-docs/index.html file and add the deployed site to the list.
|Now, you have to sign the binary packages which are in apacheds/target/checkout/target.
Use your PGP key ID (the pub key, 4096R/[XXXXXXX] where [XXXXXXX] is the key ID)
The best way to do that is to download the sources, extract them, build the server and the installers, and check if the installers are correctly working. Then check that the server is correctly running.
Start a 72h vote at the dev mailing list.
If the vote succeeds Apacheds project can be released.
Go to https://repository.apache.org/index.html#stagingRepositories and release the staging repository so all artifacts are published to Maven central.
Move the distribution packages to people.apache.org/www/www.apache.org/dist/directory/apacheds/stable.