Versions Compared

Old Version 28

changes.mady.by.user Mike Rheinheimer

Saved on

compared with

New Version 29

changes.mady.by.user Mike Rheinheimer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Check that there are no uncommitted changes in the sources
  • Check that there are no SNAPSHOT dependencies
  • Change the version in the poms from x-SNAPSHOT to a new version (you will be prompted for the versions to use)
  • Transform the SCM information in the POM to include the final destination of the tag
  • Run the project tests against the modified POMs to confirm everything is in working order
  • Commit the modified POMs
  • Tag the code in the SCM with a version name (this will be prompted for)
  • Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for. NOTE: since we're running the release from the branch, and you want this branch name to match up with the version in the pom.xml files in the branch, use the same name on this "development version" question that you used on the "release version" question. We'll update the pom.xml files in trunk by hand later.)
  • Commit the modified POMs

...

If the vote passes, you'll need to promote that staging repository to the main location. Login to Nexus to do that as well. See Maven team release page for more details.


7.

...

Copying distributions to Apache

Copy the actual distributions (all artifacts located under apache-wink in Nexus repo) to people.apache.org:/www/www.apache.org/dist/incubator/wink.

...

  • Check out Wink site from https://svn.apache.org/repos/asf/incubator/wink/site
  • Update Wink Java-Docs by:
    • Download & extract Java-Docs from distribution source archive
    • Create new directory under /wink/site/trunk/site/src/site/resources/VERSION and copy extracted Java-Docs
  • Update Wink site Download page with new Wink release artifacts
  • Follow instructions located under /wink/site/trunk/site/how-to.txt to rebuild the site

H6. 9. Update pom.xml files in trunk

Once the release is successful, and since we ran the release from a branch, the pom.xml files in trunk still have the old version number. You will want to update the version in all of the pom.xml files throughout the project; for example, from 1.1-incubating-SNAPSHOT to 1.2-incubating-SNAPSHOT.

Resources

A Guide To Release Management During Incubation http://incubator.apache.org/guides/releasemanagement.html