Deploying snapshots
Snapshots are automatically deployed every night to the Nexus snapshot repository at https://repository.apache.org/content/groups/snapshots-group/
. There is no need to manually deploy snapshots anymore.
Maintaining a fixes branch
dkulp: I'm adding this section to document what worked for ME when maintaining the 2.0.x-fixes branch for the 2.0.x releases. Each Release Manager may have their own style or tools or whatever. This is not a "set in stone" type thing.
Basically, almost all development and fixes and such are usually done by the various developers right on trunk. Thus, the main job of the fixes branch maintainer is to triage the commits on trunk and merge pure fixes to the fixes branch, resolve conflicts, run the tests, and periodically deploy snapshots. For the most part, when things go well, it doesn't take too much time or effort. An hour or two every couple days is about it.
To set up, you'll want to:
- use svn cp to make a branch. Use URLs for the pathnames or it will take forever.
- use bin/pom-version.pl to change the version in the branch
- use svnmerge.py init to set up svnmerge. You may want to run this in both the trunk and the new branch in case you are contemplating bidirectional merges.
These steps work for individual developers who want to go off into a branch in the sandbox to work through something complex.
In trunk/bin, there is a DoMerges.java program that wraps svnmerge.py to assist in the merging. If the branch is setup with snvmerge.py, if you run it from you checkout directory, it will prompt for every commit on trunk to see if you want to "Merge" it, "Block" it, or "Ignore" it. It displays the commit log first so you can see what was involved. You can also check the cxf-commits archive to see the full details of the commit to help decide what action to take. If you select "Merge", it will merge the change and then prompt before committing. That will allow you to look at the merge and resolve any conflicts. (or even revert it if you didn't mean to hit Merge)
Performing a release
The first step is to update the release_notes.txt in the distribution/src/main/release.
Then, to actually perform the relesae, run the below commands.
Make sure you use Maven 2.2.1, not Maven 3.x. There is a bug that causes the signatures of the projects of packaging "bundle" to not be deployed correctly with Maven 3.x.
mvn release:prepare -Peverything,jaxws22 mvn release:perform
That will tag the release, update the poms, etc... Then build it (off the tag) and deploy everything (including source jars and javadoc jars) to the Nexus repository location and gpg signs everything. When the build is done staging, you need to login to the Nexus repository and "close" the staging are. That is very important. After the staging are is closed, note the URL for the staging area as you will need that for the vote.
At this point, everything "pre-vote" is done. Call the vote.
After the vote passes, you'll need to promote that staging repository to the main location. Login to Nexus to do that as well. See above Maven team release page.
Also, don't forget to copy the actual distributions to people.apache.org:/www/www.apache.org/dist/cxf.
Unpack the javadocs. Create a new directory in /www/cxf.apache.org/javadoc to match the version number and then unpack the cxf-bundle/$version/*-javadoc.jar from the maven repo into that new directory. Update the "latest" sym-links in the javadoc directory to point to the new directory.
Finally, update the download pages.