public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: "Martin Liška" <mliska@suse.cz>, FX <fxcoudert@gmail.com>
Cc: gcc@gcc.gnu.org,Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: GCC 10.2 Released
Date: Wed, 23 Dec 2020 15:25:10 +0100	[thread overview]
Message-ID: <346703CF-E479-4BED-8FF8-04E3AC0E537F@suse.de> (raw)
In-Reply-To: <e282f43f-dfeb-2c3e-dbc4-8f29a15c31a4@suse.cz>

On December 23, 2020 2:29:48 PM GMT+01:00, "Martin Liška" <mliska@suse.cz> wrote:
>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)

Since 10.2 was comparatively early we can see to do 10.3 end of January or begin of February. Note that the advantage of aligning more with 11.1 is that most of the stage 4 fixes apply to 10.x as well. 

Richard. 

>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
>> 


  parent reply	other threads:[~2020-12-23 14:25 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
2020-12-23 14:06   ` Iain Sandoe
2020-12-23 14:25   ` Richard Biener [this message]
  -- 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=346703CF-E479-4BED-8FF8-04E3AC0E537F@suse.de \
    --to=rguenther@suse.de \
    --cc=fxcoudert@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=mliska@suse.cz \
    /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).