[commons-rng] branch master updated: Release doc updates

[ah...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

aherbert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-rng.git


The following commit(s) were added to refs/heads/master by this push:
     new 60f58a6f Release doc updates
60f58a6f is described below

commit 60f58a6fbc30a0fa8a26ada9a9af8b22548b7579
Author: aherbert <ah...@apache.org>
AuthorDate: Tue Nov 29 16:27:21 2022 +0000

    Release doc updates
---
 doc/release/release.howto.txt | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/doc/release/release.howto.txt b/doc/release/release.howto.txt
index 40125908..1f86ac8e 100644
--- a/doc/release/release.howto.txt
+++ b/doc/release/release.howto.txt
@@ -75,11 +75,11 @@ NOTE
 When performing a release it is good practice to edit a copy of these notes during the process
 and merge the updated document into the repository following a release. To assist in this process
 a find-and-replace can be performed to update all the version numbers in order. For example
-based on a previous release of 1.0:
+based on a previous release of 1.5:
 
-- Next development version  : 1.1 -> 1.2
-- Next release version      : 1.0 -> 1.1
-- Previous release version  : 1.0-beta1 -> 1.0
+- Next development version  : 1.6 -> 1.7
+- Next release version      : 1.5 -> 1.6
+- Previous release version  : 1.4 -> 1.5
 - Release candidate version : RC1 -> RC2   (if applicable)
 
 This allows the included commands to be coped during the release process.
@@ -107,7 +107,8 @@ Preliminary checks:
  * Make sure that the construct reported by "SpotBugs" and "PMD" are intentional.
  * Mark all issues fixed in the release as resolved in the bug-tracking system (JIRA). Issues marked
    as 'Implemented' or 'Fixed' will appear in the changes report. Add a corresponding entry in
-   "src/changes/changes.xml" for the JIRA ticket.
+   "src/changes/changes.xml" for the JIRA ticket. To search for unresolved tickets
+   click 'Releases' on the left menu and select the upcoming release version.
 
 
 (1)