Author: chtompki Date: Thu Dec 21 02:53:31 2017 New Revision: 1818869 URL: http://svn.apache.org/viewvc?rev=1818869&view=rev Log: Adding Jira no email release closure documentation
Modified: commons/cms-site/trunk/content/xdoc/releases/release.xml Modified: commons/cms-site/trunk/content/xdoc/releases/release.xml URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/releases/release.xml?rev=1818869&r1=1818868&r2=1818869&view=diff ============================================================================== --- commons/cms-site/trunk/content/xdoc/releases/release.xml (original) +++ commons/cms-site/trunk/content/xdoc/releases/release.xml Thu Dec 21 02:53:31 2017 @@ -262,9 +262,24 @@ <li> <strong>Update JIRA</strong> Mark the release as released in the JIRA project admin and CLOSE all issues RESOLVED - in this release. Make sure the FIX VERSION for all issues closed with this release + in this release. Make sure the FIX VERSION for all issues closed with this release is set correctly to this version. If this has not already been done, create a JIRA version - for the next release. + for the next release. To prevent a slurry of emails in closing the Jira issues, do the following: + <ul> + <li>Log in to <a href="https://issues.apache.org/jira">Jira</a>.</li> + <li>Click your cursor in the search field and press enter which brings you to search.</li> + <li>Ensure that you click the "advanced" search option.</li> + <li> + In the search field enter <code>project={component_name (e.g. lang)} AND status=resolved</code>, replacing + what we have in the curly braces with the appropriate component name. + </li> + <li>Now, select "Tools" in the top right and choose "Bulk Change" for all of your relevent issues.</li> + <li>At step 1, select the issues you wish to transition.</li> + <li>At step 2, select "Transition Issues."</li> + <li>At step 3, choose close issues.</li> + <li>At step 4, enter proper comment, and deselect "Send mail for this update."</li> + <li>Click go.</li> + </ul> </li> <li> <strong>Update DOAP file</strong>