commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Commons Wiki] Update of "CreatingReleases" by sebbapache
Date Thu, 21 Feb 2008 19:08:23 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification.

The following page has been changed by sebbapache:

The comment on the change is:
DRAFT Procedure for creating a release using M2

New page:
= DRAFT Procedure for creating a release using M2 =

'''This is currently a discussion page, and is not (yet) policy''

This assumes that the Commons Proxy is about to vote on 1.0-RC3.

 * Tag "proxy-1.0-rc3"  but with the version number set to "1.0". This is so the release does
not have to be rebuilt later just to fix the version.

 * Check out the tag proxy-1.0-rc3 into a clean local working directory

 * Build the release artifacts - I think there's a couple of options here:

  * Run the following maven command:

  {{{mvn site javadoc:jar source:jar assembly:assembly}}}

  This will create all the artifacts - jars and src and binary distros,
  but then you need to create checksums and sign

  * Run the following maven command:

  {{{mvn -Prc -DcreateChecksum=true site install}}}

  This should create all the artifacts installed in your local m2
  repository, signed and checksums  (note it also creates checksums for
  signature files - I delete those)

 * Upload the artifacts to<userid>/proxy-1.0-rc3 (e.g.) and call
a vote on dev@

 * Make sure that the KEYS file is in SVN and the signing key has been added to it.

 * The vote e-mail should include:

  * URL for artifacts
  * URL for SVN tag
  * URL for website

 * If the VOTE passes, then the RC tag can just be copied to the formal release tag, i.e.
without the RC suffix. The RC tag should be kept.

 * If the VOTE fails, the failed RC tag can be deleted if required.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message