public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 11.2.1 Status Report (2022-04-13), branch frozen for release
Date: Wed, 13 Apr 2022 09:30:07 +0200 (CEST)	[thread overview]
Message-ID: <6n6n1o1q-7qs3-s42-2q28-9q4s3879517o@fhfr.qr> (raw)


Status
======

The gcc-11 branch is now frozen in preparation for a GCC 11.3 release
candidate and the GCC 11.3 release next week.  All changes now require
release manager approval.

The remaining P1 bugs have been resolved or pushed back to GCC 11.4.

Quality Data
============

Priority          #   Change from last report
--------        ---   -----------------------
P1              0     -   3
P2              422   -  26
P3              55    -   8
P4              233   +  10
P5              25
--------        ---   -----------------------
Total P1-P3     477   -  37
Total		735   -  27


Previous Report
===============

https://gcc.gnu.org/pipermail/gcc/2022-April/238504.html

             reply	other threads:[~2022-04-13  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  7:30 Richard Biener [this message]
2022-04-14  7:11 ` Andreas Krebbel
2022-04-14  8:02   ` Richard Biener

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6n6n1o1q-7qs3-s42-2q28-9q4s3879517o@fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).