From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: GCC 12.2.1 Status Report (2023-05-02), branch frozen for release
Date: Tue, 2 May 2023 06:54:54 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2305020650470.4466@jbgna.fhfr.qr> (raw)
The GCC 12 branch is now frozen in preparation for a GCC 12.3 release
candidate and the release of GCC 12.3 next week.
All changes require release manager approval.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 0 - 1
P2 502 - 28
P3 49 - 7
P4 232 - 4
P5 24
-------- --- -----------------------
Total P1-P3 551 - 36
Total 807 - 40
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2023-April/241138.html
reply other threads:[~2023-05-02 6:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=nycvar.YFH.7.77.849.2305020650470.4466@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=fortran@gcc.gnu.org \
--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).