converted to 1.6 markup
|No differences found!|
Release 1.0.5 Log
This is not so much a "Release Plan" page as it is a log of the procedures used to produce the upcoming 1.0.5 release. It will be updated as procedures are done.
Release Master POM
Used the following 2 commands to release the master pom.
mvn release:prepare -Dusername=YOURUSERNAME -Dpassword=YOURPASSWORD mvn release:perform -Dusername=YOURUSERNAME -Dpassword=YOURPASSWORD
It appears the release:perform step copied over the shale.apache.org site. We need to figure out how to tell it not to do this.
Maven did not do the GPG signing bit so I performed the following steps:
cd target/checkout gpg --armor --output shale-master-3.pom.asc --detach-sig pom.xml scp shale-master-3.pom.asc people.apache.org:/www/people.apache.org/builds/shale/m2-staging-repository/org/apache/shale/shale-master/3/.
Then to correct the file permissions on people.apache.org:
chmod 664 /www/people.apache.org/builds/shale/m2-staging-repository/org/apache/shale/shale-master/3/shale-master-3.pom.asc
Called for a release vote using the following text.
This is the formal vote for the new Shale master POM version 3. I would appreciate a thorough review of these artifacts since I am a release manager newbie :-) You can find the signed release candidate at . Please vote +1 if you reviewed the new master pom and approve of it -1 if you found a flaw or potential problem with the new master pom Thanks, Greg  http://people.apache.org/builds/shale/m2-staging-repository/org/apache/shale/shale-master/3/
Copy release artifacts from staging area to live repository:
cp -r /www/people.apache.org/builds/shale/m2-staging-repository/org/apache/shale/shale-master /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/shale/.
Followed steps outlined in ReleaseProcess to edit Jira.
- Added Jira version 1.0.5
- Moved 2 unresolved issues from 1.0.5-SNAPSHOT to Unknown
- Moved 32 remaining issues from 1.0.5-SNAPSHOT to 1.0.5.
- Archived 1.0.5-SNAPSHOT
Created release-notes-1.0.5.html document for release notes.
Do a dry run of the release prepare to see what it generates:
mvn -DdryRun=true -Prelease,apps,dist clean release:prepare
Run Maven release process on 1_0_X branch:
On at least one instance trying to do a full shale build I had to give Maven more memory to work with:
MAVEN_OPTS="-Xmx1024m -Xms512m" export MAVEN_OPTS
mvn -Dusername=SVN_USERNAME -Dpassword=SVN_PASSWORD -Prelease,apps,dist clean release:prepare mvn -Dusername=SVN_USERNAME -Dpassword=SVN_PASSWORD -Prelease,apps,dist clean release:perform