public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
	Florian Weimer <fweimer@redhat.com>
Subject: glibc 2.35 - Status update: ABI freeze, and release blockers.
Date: Thu, 27 Jan 2022 00:11:51 -0500	[thread overview]
Message-ID: <3d98ce14-6c91-35c2-987b-73d0382ce39b@redhat.com> (raw)

Community,

The glibc 2.35 release machine testing should start shortly. I'll
send a distinct email about that.

Please consider the ABI frozen. Any ABI changes should be OK'd with
the release manager.

(a) Blockers.

(a.1) LD_AUDIT fixes.

I'm an reviewing the LD_AUDIT fixes (series 6823). I would like to see
these fixes go in.

(a.2) glibc 2.34 ABI omission patch.

Florian,

What is the current status of the glibc 2.34 ABI omission patch?

I did a review here:
https://sourceware.org/pipermail/libc-alpha/2022-January/135271.html

I think we should commit what you have, and look at HJ's suggestions
for the future as you noted here:
https://sourceware.org/pipermail/libc-alpha/2022-January/135635.html

(a.3) ancillary 64-bit time timestamp conversion.

Adhemerval,

What is the current status of the ancillary 64-bit time timestamp
conversion fixes?

(b) Desirable.

(b.1) Predictable ELF destructor ordering.

Florian,

We haven't had much time to review this, and I'd like to spend more
time reviewing the changes and testing in Fedora. Would it be OK if
we keep reviewing this and commit early in February? This would give
us lots of time to include this in Fedora Rawhide and other rolling
releases to look for issues.

(b.2) pthread condvar stealing bug.

I'm going to switch to reviewing this right after (a.1), and if we
get a fix after the relase we can backport to the release branch,
but I won't hold the release for this bug.


-- 
Cheers,
Carlos.


             reply	other threads:[~2022-01-27  5:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  5:11 Carlos O'Donell [this message]
2022-01-27  9:53 ` Florian Weimer
2022-01-27 16:15 ` Stefan Liebler

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=3d98ce14-6c91-35c2-987b-73d0382ce39b@redhat.com \
    --to=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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).