Page History

...

Snapshots are automatically deployed every night to the Nexus snapshot repository at https://repository.apache.org/content/groups/snapshots-group/^{Image Removed} . There is no need to manually deploy snapshots anymore.

...

dkulp: I'm adding this section to document what worked for ME when maintaining the 2.07.x-fixes branch for the 2.07.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 trunkmaster. Thus, the main job of the fixes branch maintainer is to triage the commits on trunk master and merge pure fixes to the fixes branchbranches, 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:

1. use svn cp git branch to make a branch. Use URLs for the pathnames or it will take forever.
2. use bin/pom-version.pl to change the version in the branch
3. 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.

2. On the branch, create a .gitmergeinfo file with a single line of "origin/master" to say the branch will be merging from there.

In trunk/bin, there is a DoMerges.java program that wraps svnmerge.py to assist assists in the merging. If the branch is setup with snvmerge .pygitmergeinfo, if you run it from you the root directory of the checkout directory, it will prompt for every commit on trunk master 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. This file's JIRA list of solved Bugs, Improvements, etc. can be obtained from the "Road Map" JIRA tab, selecting the desired version's Release Notes, and then the Configure Release Notes button (choose Text output).

...
<server>                                                                
   <id>apache.releases.https</id>
   <username>apacheID</username>
   <password>yourLDAPPassword</password>
</server>
...

Then, to actually perform the release, run the below commands.

mvn release:prepare -Peverything
mvn release:perform -Peverything

The above commands tag the release, update the poms versions, etc., then build it (off the tag), gpg sign and deploy everything (including source jars and javadoc jars) to the Nexus repository location. When the build is done staging, you next need to login to the Nexus repository and "close" the staging area (click on Staging Repositories in the left-side menu, select the repo you just uploaded and then select the close button.) Closing is very important. After the staging area is closed, note the URL for the staging area as you will need that for the vote.

...

...

You may encounter error like
INFO Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: PROPFIND request failed on '/repos/asf/!svn/vcc/default'
svn: No such revision 1197023
when run "mvn release:prepare -Peverything,jaxws22" to create tag if you're not in U.S.
This is caused by that the svn server in Europe need some time to sync up to the central server in U.S.
If you encounter it, just wait a minute, and do "mvn release:prepare -Dresume=true -Peverything,jaxws22" which
will pick up the left task from last run.

At this point, everything "pre-vote" is done. Call the vote.

...

• Maven artifacts - After the vote passes, you'll need to promote that staging repository to the main location. Login to Nexus repository location to do that as well. See above Maven team release page., find the staging repository and click the Release button.

• Distributions - You will need to commit the distributions into the special svn distribution area: https://dist.apache.org/repos/dist/release/cxf

  ^{Image Removed}

  
  

  when the commit done there,

  after you commit they will be live on dist.apache.org fairly quickly, but it will still take time for the mirrors to get copies. It's likely easier to make the directory via an svn command, check out just that directory, and then add the files. The dist area is rather large (400MB or so) so checking out the entire thing may be slow.

  Code Block
  svn mkdir https://dist.apache.org/repos/dist/release/cxf/2.6.3 svn checkout https://dist.apache.org/repos/dist/release/cxf/2.6.3 .... add files to 2.6.3 ..... svn commit

  
  

The download page of a currently released version will tell you the precise files you need to upload. Basically, the -src.tar.gz, -src.zip, tar.gz, .zip files, and the .md5, .sha1, and .asc signature files of each of those. For greatest accuracy, it's best to download the files from Nexus and use those. (For example, for CXF 2.6.2, you would check this folder).

• Update the download page - around 24 hours after committing the distributions, update the download page, release notes, etc. .. to point at the new versions. At that stage you'll want to delete (svn rm) the previous version of each branch you uploaded to https://dist.apache.org, so if you added https://dist.apache.org/repos/dist/release/cxf/2.6.3 and https://dist.apache.org/repos/dist/release/cxf/2.5.6, you'll want to remove https://dist.apache.org/repos/dist/release/cxf/2.6.2 and https://dist.apache.org/repos/dist/release/cxf/2.5.5. (Older versions will still be available at http://archive.apache.org/dist/cxf/ and are referenced from there on the CXF download page.)

• Javadocs - the javadocs in the distribution are a limited set of javadocs useful for MOST people.  However, the CXF website contains a more complete set of javadocs.  To generate the docs for the site, from the source distribution (or git tag), run:

  Code Block
  mvn javadoc:aggregate mvn package -DskipTests=true javadoc:aggregate-no-fork -pl distribution -am -Peverything -Dmaven.javadoc.skippedModules=cxf-testutils

  The first call (which WILL fail while trying to process some of the system tests) makes sure all the necessary things are built, code generated, etc...   The second call will generate the javadoc for the site.  Then copy the contents of target/site/apidocs to a new versioned directory in

  Unpack the javadocs from the appropriate cxf-bundle-VERSION-javadocs.jar into the appropriate directory in

  an svn checkout of https://svn-master.apache.org/repos/infra/websites/production/cxf/content/javadoc

  ^{Image Removed}

  and commit the new version. Make sure any new files are added.

• Unpack the schemas directory from the appropriate cxf-bundle-VERSION.jar and check if any of the schemas in https://svn-master.apache.org/repos/infra/websites/production/cxf/content/schemas^{Image Removed} need updating need updating.

Updating JIRA

JIRA will need to be updated:

• Add new versions that JIRA items can be created against, and mark the version(s) you just released as "released":

1. Go to the CXF JIRA Home Page and select the "Versions" left menu item, then select "Manage Versions".
2. Select the tools icon (far right side) for the version(s) you've just released and select "Release".
3. Also on this screen type in new release versions for the branch(es) you've released and plan on releasing more versions from.

• Close the JIRA items that were marked resolved for each release:

1. From the previous screen, select "Exit Administration".
2. From the CXF JIRA home page, select Versions from the left-side menu, and for each version you just released:
   1. Select version, then issues left-side menu item, then select the "Resolved" list.
   2. From the tools icon, select Bulk Change -> select all items -> Transition Issues -> Close Issues -> Confirm.