From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: fortran@gcc.gnu.org
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Subject: Fw: GCC 13.0.1 Status Report (2023-04-17)
Date: Mon, 17 Apr 2023 20:46:55 +0200 [thread overview]
Message-ID: <20230417204655.2eefe31f@nbbrfq> (raw)
fyi
Begin forwarded message:
Date: Mon, 17 Apr 2023 15:54:45 +0200
From: Jakub Jelinek via Gcc-patches <gcc-patches@gcc.gnu.org>
To: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: GCC 13.0.1 Status Report (2023-04-17)
Status
======
We have reached zero P1 regressions today and releases/gcc-13 branch has
been created. GCC 13.1-rc1 will be built likely tomorrow.
The branch is now frozen for blocking regressions and documentation
fixes only, all changes to the branch require a RM approval now.
If no show stoppers appear, we'd like to release 13.1 next week,
or soon after that, if any important issues are discovered and
fixed, rc2 could be released next week.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 0 - 32
P2 492
P3 57 - 20
P4 241 - 14
P5 24
-------- --- -----------------------
Total P1-P3 549 - 52
Total 814 - 66
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2023-February/240765.html
reply other threads:[~2023-04-17 18:47 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=20230417204655.2eefe31f@nbbrfq \
--to=rep.dot.nop@gmail.com \
--cc=fortran@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).