gcc-wwwdocs branch master updated. 4ae43876bc9ed2bd5a4002952f3f4565be62d726

gcc-wwwdocs branch master updated. 4ae43876bc9ed2bd5a4002952f3f4565be62d726

[Martin Liska]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  4ae43876bc9ed2bd5a4002952f3f4565be62d726 (commit)
      from  dff8f587116f9a81b545dad0557d3ae90e58a6d6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 4ae43876bc9ed2bd5a4002952f3f4565be62d726
Author: Martin Liska <mliska@suse.cz>
Date:   Fri Apr 9 10:44:44 2021 +0200

    Document branch_changer.py and its usage.

diff --git a/htdocs/branch-closing.html b/htdocs/branch-closing.html
index 2a4f9d21..d9c18c44 100644
--- a/htdocs/branch-closing.html
+++ b/htdocs/branch-closing.html
@@ -47,21 +47,36 @@ closed (for example, "7.5.0" if the branch is being closed when that
 is the version number a compiler built from the branch would report)
 is listed in "Known to work" or "Known to fail" as applicable.</li>
 
+<li>If the bug is a regression that is not fixed on all subsequent
+release branches and on trunk then it needs to remain open.  Remove
+the version number of the branch being closed from the summary (for
+example, change "[7/8 Regression]" to "[8 Regression]".  If the
+milestone is not set, or is set to a version from the branch being
+closed, set it to the version number of the next release from the next
+oldest release branch.
+
+The step can be done by <code>maintainer-scripts/branch_changer.py</code> script
+with the following arguments:
+<code>./branch_changer.py api_key --new-target-milestone=8.5:9.4 --remove 8
+--comment 'GCC 8 branch is being closed.'</code>
+
+The script invocation changes target milestone from 8.5 to 9.4 and removes
+'/8' from a '[Regression x/y/z]' summary line.  Moreover, a new comment is added.
+
+Unless you add <strong>--doit</strong>, the script runs in dry mode only.
+</li>
+
 <li>If the bug is not a regression and is fixed on trunk, or if it is
 a regression but is fixed on all subsequent release branches and on
 trunk, it should be marked FIXED.  "Known to work" and "Known to fail"
 should be updated to indicate the passing and failing versions on
 subsequent release branches.  The target milestone should be set to
 the earliest version in which the bug was fixed within the first
-release branch on which it was fixed.</li>
+release branch on which it was fixed.
 
-<li>If the bug is a regression that is not fixed on all subsequent
-release branches and on trunk then it needs to remain open.  Remove
-the version number of the branch being closed from the summary (for
-example, change "[7/8 Regression]" to "[8 Regression]".  If the
-milestone is not set, or is set to a version from the branch being
-closed, set it to the version number of the next release from the next
-oldest release branch.</li>
+Re-run the same script command from the previous step in order to get list
+of all PRs that can be closed.  This script will list them now.
+</li>
 
 </ol></li>
 
diff --git a/htdocs/releasing.html b/htdocs/releasing.html
index c92f06bc..89f342b3 100644
--- a/htdocs/releasing.html
+++ b/htdocs/releasing.html
@@ -144,11 +144,25 @@ Please do <strong>not</strong> delete old target milestones.</li>
 
 <li>Change all open bugs targeted at the just released milestone to be targeted
 at either the mainline version milestone, or the next point-release milestone.
-This can be accomplished by querying for all bugs targeted at the old
-milestone, choosing "Change several bugs at once" at the bottom of the
-buglist screen, choosing "check all" to select all bugs to change, 
-choosing the new target milestone from the drop down, entering a
-useful comment, and clicking commit. </li>
+This can be accomplished by
+<code>maintainer-scripts/branch_changer.py</code> script with the following arguments:
+<code>./maintainer-scripts/branch_changer.py api_key --new-target-milestone=10.4:10.5
+--comment 'GCC 10.4 is being released, retargeting bugs to GCC 10.5.'</code>
+
+The script invocation changes target milestone from 10.4 to 10.5 and new comment
+<i>GCC 10.4 is being released, retargeting bugs to GCC 10.5.</i> is added.
+
+Unless you add <strong>--doit</strong>, the script runs in dry mode only. One can use
+<code>--limit N</code> in order to limit the number of affected bugs.
+
+<li>If you release a first branch release (e.g. 11.1.0), bug regression summary needs
+to adjusted by <code>maintainer-scripts/branch_changer.py</code> with the following arguments:
+<code>./maintainer-scripts/branch_changer.py api_key --add=11:12</code>
+
+The script adds '/12' to all PRs marked with a '[Regression x/y/z]' summary line.
+
+Again, unless you add <strong>--doit</strong>, the script runs in dry mode only.
+</li>
 
 <li>Update the bug searches on the main web page for the milestone
 changes.</li>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/branch-closing.html | 31 +++++++++++++++++++++++--------
 htdocs/releasing.html      | 24 +++++++++++++++++++-----
 2 files changed, 42 insertions(+), 13 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs