|$ cd ~/apacheds/production/content/apacheds/gen-docs |
$ mkdir <version>
|$ svn add <version> |
|$ cp -r ~/apacheds/trunks/apacheds/target/checkout/target/site/apachedsdocs ~/apacheds/trunks/apacheds/target/checkout/target/site/apidocs ~/apacheds/production/content/apacheds/gen-docs/<version> |
|$ cp -r ~/apacheds/trunks/apacheds/target/checkout/target/site/xref ~/apacheds/production/content/apacheds/gen-docs/<version> |
|$ svn add <version>/* |
|$ svn ci <version> -m "Injected <version> javadocs" |
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.
The current apacheds/pom.xml contains references to LDAP API SNAPSHOTs, which is not good. You have to bump up those references to the latest LDAP-API version.
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.
In order to generate the site, you have to comment some modules in the apacheds pom.xml file :
Then you can start the maven command :
This creates the site and the Javadocs.
|Now, you have to sign the sources packages which are in apacheds/target/checkout/target.
Use your PGP key ID (the pub key, 4096R/[XXXXXXX] where [XXXXXXX] is the key ID)
You can get the keys by typing :
You can use this small script that does the job (copy-paste this code in a file named sign.sh in your path) :
Then to sign the packages :
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.
We now have to create the installers. Go into the target/checkout directory and run :
This will create the installers in the target/checkout/installers/target/installers directory
Sign those installers using the sigh.sh script, and copy them in people.apache.org/public_html/apacheds-<version>
Note : you will need a Debian, a Fedora and a Windows server to generate dedicated binaries for those platforms, or you can use rpmbuild, dpkg or nsis if you don't want to use many different servers.
Update your index.html file on people.apache.org/public_html to make the packages visible. Here is an example of possible content :
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 (sources and binaries) to the dist SVN repository: https://dist.apache.org/repos/dist/release/directory/apacheds/dist/$(version)
The best solution would be to checkout the directory in people.apache.org, to copy the packages in the right place, and to check in the changes :
The packages should now be available on http://www.us.apache.org/dist/directory/api/dist/<version>
We now can deploy the generated Javadoc and cross-reference pages. They are generated in the following directory :
We will copy two directories :
*Staging or Production?*
Those files will be stored on the production server only !!! And some extra caution ust be taken not to delete them when we will publish the staging site too...
First of all, you must checkout the two CMS store for the site : staging and revision.
Now, you will first add the directory for the newly generated version :
Then copy the generated docs :
You have to check in those directories :
Now, you have to update the staging site :
This file list the file on the production site that will not be overriden by the publication of the staging site. It has to be updated
Add the following line :
then save and check in the file .htaccess
We also have to update this file :
And update the two last lines to refer to the version you've just released :
Save and commit the file.
You can now update the site, add a news on the front page, and publish the site.
After 24h, you can now inform the world about the release.
Send a mail to the users and dev mailing list, and one to the firstname.lastname@example.org.
You are done !