From: Matthias Klose <doko@ubuntu.com>
To: Nick Clifton <nickc@redhat.com>, Binutils <binutils@sourceware.org>
Subject: Re: 2.39 Release Schedule
Date: Fri, 1 Jul 2022 06:08:18 +0200 [thread overview]
Message-ID: <7a8e42b4-942d-e294-1d90-3418a5919817@ubuntu.com> (raw)
In-Reply-To: <9e7bc498-5598-baaa-3b40-001aa7e772a8@redhat.com>
On 27.06.22 13:37, Nick Clifton via Binutils wrote:
> Hi Guys,
>
> OK, so the plan is that the branch for the 2.39 release will be
> cut on Friday July 8th (just before I go on vacation). All being
> well the release itself will happen in the first weekend of August
> (Sat 6th probably).
>
> If you have new features that you want to get into the 2.39 release
> now is the time to submit them - or ping for a review if they have
> already been submitted.
>
> Once the branch is cut the usual rules will apply - bug fixes and
> doc updates only - although this time around I am also going to ask
> that any maintainer who wishes to do so review and approve/reject
> patches for the branch.
>
> I will be away July 11..July 22 but as soon as I get back I will be
> on patch review duty for as much of the time as I can.
there seems to be one more regression building GCC in some configurations on
aarch64-linux-gnu, filed
https://sourceware.org/bugzilla/show_bug.cgi?id=29310
it looks like I cannot see that with a binutils trunk build from 20220615, and
2.38 also works fine.
Matthias
prev parent reply other threads:[~2022-07-01 4:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 11:37 Nick Clifton
2022-06-27 18:43 ` Matthias Klose
2022-06-28 1:03 ` Alan Modra
2022-07-01 4:08 ` Matthias Klose [this message]
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=7a8e42b4-942d-e294-1d90-3418a5919817@ubuntu.com \
--to=doko@ubuntu.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/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).