[Shale Wiki] Update of ReleaseProcess by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/shale/ReleaseProcess The comment on the change is: From SHALE-319, distribution management repository has changed. -- + === 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)
[Shale Wiki] Update of ReleaseProcess by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/shale/ReleaseProcess The comment on the change is: Capture Sean's JIRA instructions. New page: === 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.
