From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 1851) id EFA2B398D048; Fri, 9 Apr 2021 12:55:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EFA2B398D048 To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 4ae43876bc9ed2bd5a4002952f3f4565be62d726 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: dff8f587116f9a81b545dad0557d3ae90e58a6d6 X-Git-Newrev: 4ae43876bc9ed2bd5a4002952f3f4565be62d726 Message-Id: <20210409125522.EFA2B398D048@sourceware.org> Date: Fri, 9 Apr 2021 12:55:22 +0000 (GMT) From: Martin Liska X-BeenThere: gcc-cvs-wwwdocs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-cvs-wwwdocs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2021 12:55:23 -0000 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 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. +
  • 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 maintainer-scripts/branch_changer.py script +with the following arguments: +./branch_changer.py api_key --new-target-milestone=8.5:9.4 --remove 8 +--comment 'GCC 8 branch is being closed.' + +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 --doit, the script runs in dry mode only. +
    • +
  • 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.
    • +release branch on which it was fixed. -
  • 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.
    • +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. + 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 not delete old target milestones.
  • 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.
    • +This can be accomplished by +maintainer-scripts/branch_changer.py script with the following arguments: +./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.' + +The script invocation changes target milestone from 10.4 to 10.5 and new comment +GCC 10.4 is being released, retargeting bugs to GCC 10.5. is added. + +Unless you add --doit, the script runs in dry mode only. One can use +--limit N in order to limit the number of affected bugs. + +
  • If you release a first branch release (e.g. 11.1.0), bug regression summary needs +to adjusted by maintainer-scripts/branch_changer.py with the following arguments: +./maintainer-scripts/branch_changer.py api_key --add=11:12 + +The script adds '/12' to all PRs marked with a '[Regression x/y/z]' summary line. + +Again, unless you add --doit, the script runs in dry mode only. +
  • Update the bug searches on the main web page for the milestone changes.
    • ----------------------------------------------------------------------- Summary of changes: htdocs/branch-closing.html | 31 +++++++++++++++++++++++-------- htdocs/releasing.html | 24 +++++++++++++++++++----- 2 files changed, 42 insertions(+), 13 deletions(-) hooks/post-receive -- gcc-wwwdocs