From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 1851) id 2401D3968C36; Mon, 19 Apr 2021 12:56:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2401D3968C36 To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 6b788fa278b4f863a17ab80e0bf4991c3d8de167 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: 58d5405b469b0bc67d2c763778447f883d4f640d X-Git-Newrev: 6b788fa278b4f863a17ab80e0bf4991c3d8de167 Message-Id: <20210419125618.2401D3968C36@sourceware.org> Date: Mon, 19 Apr 2021 12:56:18 +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: Mon, 19 Apr 2021 12:56:18 -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 6b788fa278b4f863a17ab80e0bf4991c3d8de167 (commit) from 58d5405b469b0bc67d2c763778447f883d4f640d (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 6b788fa278b4f863a17ab80e0bf4991c3d8de167 Author: Martin Liska Date: Mon Apr 19 14:55:54 2021 +0200 Move branch_changer.py usage to branching.html. diff --git a/htdocs/branching.html b/htdocs/branching.html index a9dafdd3..f30a47e1 100644 --- a/htdocs/branching.html +++ b/htdocs/branching.html @@ -97,9 +97,15 @@ delete old target milestones. release on the branch. For example, when branching 3.4, create a milestone for 3.4.1 for PRs that can't be fixed in time for 3.4.0. -
  • Ask Daniel Berlin to adjust all PRs with the just-branched version -in their summary to also contain the new version corresponding to -mainline.
    • +
  • 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. +
    • diff --git a/htdocs/releasing.html b/htdocs/releasing.html index df6b93dc..d51d6fc7 100644 --- a/htdocs/releasing.html +++ b/htdocs/releasing.html @@ -157,17 +157,6 @@ The script invocation changes target milestone from 10.4 to 10.5 and new comment 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/branching.html | 12 +++++++++--- htdocs/releasing.html | 11 ----------- 2 files changed, 9 insertions(+), 14 deletions(-) hooks/post-receive -- gcc-wwwdocs