[MRELEASE-341] support release process that use a staging repository

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-8
• Fix Version/s: 2.0-beta-8
• Assignee: nicolas de loof
• Reporter: nicolas de loof
• Created: 07/May/08 07:16
• Updated: 07/May/08 12:30
• Resolved: 07/May/08 10:14

Description

Many release process (ex: geronimo) require the release candidate to be exposed in a staging repository for testing, then vote from the communiity, and finally copy the artifact in the public repository / web site. This requires to run the release:perform with the final version (not a "-rc*" one).

When the vote fails, the release manager has to rollback the project to the previous SNAPSHOT version. As release:perform removes all the release-related files (including pom backups) the release:rollback goal cannot be used for this.

Geronimo solution is to copy the trunk as a "savepoint" before staging a release. A far better option would be to have a dedicated goal for this "release:stage" :

• same features as release:perform
• don't remove release.properties and backups
• requires a stagingRepository parameter, to be passed as -DaltRepoLocation to the deploy plugin
• detect the site:deploy goal and replace it with site:stage-deploy

Issue Links

• is related to: MRELEASE-340 Don't store the scm password in plaintext in release.properties