Differences between revisions 3 and 4
Revision 3 as of 2006-12-17 19:28:42
Size: 1659
Editor: WendySmoak
Comment:
Revision 4 as of 2009-09-20 21:52:43
Size: 1659
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

Build and Deploy the release

Maven artifacts are staged under http://people.apache.org/builds/shale/m2-snapshot-repository.

Each build should be staged separately, so once the build is complete, move the 'm2-snapshot-repository' underneath the (for example) builds/shale/shale-1.0.4 directory.

Archive the SNAPSHOT version in JIRA

1.) Create a new JIRA version for the release (ex. 1.0.3)

2.) Search and then bulk change unresolved issues with a "fix for" of the old snapshot version (ex. 1.0.3-SNAPSHOT) and change to "Unknown." At this point in the process, there shouldn't be any issues left on the roadmap but do a search (and bulk change) if necessary. For all bulk changes be sure to uncheck the "Send mail for this update" option on Step 3.

3.) Search and then bulk change resolved issues with a "fix for" of the old snapshot version (ex. 1.0.3-SNAPSHOT) and change to the new version (ex. 1.0.3). For all bulk changes be sure to uncheck the "Send mail for this update" option on Step 3.

4.) Archive the old version. This allows you to still search on issues that were *reported* against a SNAPSHOT version yet it prevents you from reporting new issues against the SNAPSHOT.

Assembly Plugin Notes

As of 2006-12-17, the shale-dist module is configured to use an older release of the assembly plugin, v2.0.1.

The latest release of the assembly plugin (v2.1) is ignoring the <dependencySets> element in the descriptor, so we don't get the 'lib' directory with the jars.

In a snapshot of 2.2, <dependencySets> appears to be working, so we should be able to switch once it is released.

ReleaseProcess (last edited 2009-09-20 21:52:43 by localhost)