public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: FX <fxcoudert@gmail.com>, rguenther@suse.de
Cc: gcc@gcc.gnu.org, Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: GCC 10.2 Released
Date: Wed, 23 Dec 2020 14:29:48 +0100	[thread overview]
Message-ID: <e282f43f-dfeb-2c3e-dbc4-8f29a15c31a4@suse.cz> (raw)
In-Reply-To: <1B15717E-D917-4402-B6A1-C0DE6A7B6D0D@gmail.com>

On 12/23/20 11:49 AM, FX via Gcc wrote:
> Hi all,
> 
> The gcc 10.2 release was 5 months ago today. A lot has happened in the gcc-10 branch since, in particular on aarch64. Could a new release be issued? It would make efforts at maintaining patches on top of the gcc-10 branch easier, in particular in view of the release of aarch64-apple-darwin machines.

Hello.

I understand your situation, but based on our release schedule, please expect 10.3 to
be released at the beginning of March 2021, similarly to what we did for 9.3 and 8.3:

GCC 9.3 release (2020-03-12)
GCC 8.3 release (2019-02-22)

as seen here:
https://gcc.gnu.org/develop.html

Note that making a release consumes some cycles mainly for release managers.

Thanks for understanding,
Martin

> 
> Cheers,
> FX
> 


  reply	other threads:[~2020-12-23 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23 10:49 FX
2020-12-23 13:29 ` Martin Liška [this message]
2020-12-23 14:06   ` Iain Sandoe
2020-12-23 14:25   ` Richard Biener
  -- strict thread matches above, loose matches on Subject: below --
2020-07-23  7:14 Richard Biener
2020-07-23  8:32 ` ireng ajah
2020-07-23 11:19   ` Jonathan Wakely
2020-07-23 11:20     ` Jonathan Wakely

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=e282f43f-dfeb-2c3e-dbc4-8f29a15c31a4@suse.cz \
    --to=mliska@suse.cz \
    --cc=fxcoudert@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=rguenther@suse.de \
    /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).