summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2019-03-21 09:58:23 +0000
committerintrigeri <intrigeri@boum.org>2019-03-21 09:58:23 +0000
commitf2ad5b9465e392b09a1d5509eb0180bc54e34d22 (patch)
treeb63bab332b774a7a8e4f44251192240880519f87
parent839c4dfdf8fe52c5b4d62060d3d1608fbfff02c7 (diff)
Release process: document bulk-edits for Redmine (Closes: #16588)
-rw-r--r--wiki/src/contribute/release_process.mdwn9
1 files changed, 8 insertions, 1 deletions
diff --git a/wiki/src/contribute/release_process.mdwn b/wiki/src/contribute/release_process.mdwn
index 55c88dc..b341b86 100644
--- a/wiki/src/contribute/release_process.mdwn
+++ b/wiki/src/contribute/release_process.mdwn
@@ -1316,8 +1316,15 @@ tracker. For a list of candidates, see:
* the "Fix committed" section on the *Release Manager View for ${VERSION:?}*
in Redmine.
+Select these issues with the checkboxes in the first column, then
+right click on the list to display the context menu, and finally
+change the _Status_ there. Relationships between tickets will likely
+prevent you from closing all these issues at once, but at least
+you can process them in several smaller batches instead of one by one.
+
Postpone to next release any remaining open issue for the version
-you've just released.
+you've just released. Use the right-click contextual menu to do so in
+one single batch.
Then, mark the just-released Redmine milestone as done: go to the
target version page, click *Edit*, and set *Status* to *Closed*.