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>
Subject: glibc 2.34 - Hard ABI freeze effective immediately.
Date: Sun, 18 Jul 2021 22:15:35 -0400	[thread overview]
Message-ID: <4b8bcc59-362a-21ac-b531-6be07d0c722a@redhat.com> (raw)
In-Reply-To: <7dd68a51-0904-98f8-e4ce-3e4bdcb14dc4@redhat.com>

On 7/4/21 10:43 PM, Carlos O'Donell wrote:
> We are in slushy freeze right now. I'm reviewing the last of the ABI
> changes we want to make in glibc 2.34.

The ABI freeze is now hard freeze, I would like to avoid any further ABI
changes that are not on this list.

If you have an ABI change please reach and respond to this thread 
immediately with the request.

I would like to spend this week and next fixing any remaining bugs
and doing machine testing.
 
> The ABI changes that are currently under review:
> 
> - Move nss_dns into libc.
> https://patchwork.sourceware.org/project/glibc/list/?series=2407

I have reviewed v2 and I think it should be included in 2.34.

I have just reviewed the final v3 changes so this should go in on Monday.
 
> - Remove malloc hooks.
> https://patchwork.sourceware.org/project/glibc/list/?series=2406

I have reviewed v8 and I think it should be included in 2.34.

I'll review a v9 for inclusion.

> - nss_files move.
> https://patchwork.sourceware.org/project/glibc/list/?series=2386

This was reviewed by Adhemerval and committed July 7th.

> - Add close_range, closefrom, and posix_spawn_file_actions_closefrom_np
> https://patchwork.sourceware.org/project/glibc/list/?series=2363

This was committed by Adhemerval on July 8th.

> - Define PTHREAD_STACK_MIN to sysconf(_SC_THREAD_STACK_MIN)
> https://patchwork.sourceware.org/project/glibc/list/?series=2345

I have reviewed this, and it was committed by HJ on July 9th.

> - x86: Install <bits/platform/x86.h> [BZ #27958]
> https://patchwork.sourceware.org/project/glibc/list/?series=2272

I have reviewed this and requested some changes.

I have reviewed this again and I am discussing the final wording with HJ.

I think this should be included in glibc 2.34 and we will get there.

-- 
Cheers,
Carlos.


  reply	other threads:[~2021-07-19  2:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05  2:43 glibc 2.34 - Slushy " Carlos O'Donell
2021-07-19  2:15 ` Carlos O'Donell [this message]
2021-07-19 13:51   ` glibc 2.34 - Hard ABI " Florian Weimer
2021-07-19 14:13     ` Adhemerval Zanella
2021-07-19 14:30       ` Florian Weimer
2021-07-22 12:28         ` Carlos O'Donell
2021-07-22 13:02           ` Carlos O'Donell
2021-07-22 17:56             ` Florian Weimer
2021-07-22 12:31   ` Carlos O'Donell
2021-07-22 13:24     ` Adhemerval Zanella
2021-07-23  5:13       ` Carlos O'Donell
2021-07-23  5:53         ` Siddhesh Poyarekar
2021-07-26 14:22           ` Carlos O'Donell
2021-07-26 14:28             ` Samuel Thibault
2021-07-26 14:37               ` Siddhesh Poyarekar
2021-07-26 14:45                 ` Samuel Thibault
2021-07-23 13:13         ` Adhemerval Zanella
2021-07-26 13:00           ` Carlos O'Donell
2021-07-26 13:13             ` Adhemerval Zanella
2021-07-26 18:31             ` Adhemerval Zanella
2021-07-22 13:51     ` Siddhesh Poyarekar
2021-07-25 19:46   ` H.J. Lu
2021-07-25 21:54     ` Florian Weimer
2021-07-25 22:07       ` H.J. Lu
2021-07-25 22:14         ` Florian Weimer
2021-07-26  7:19         ` Andreas Schwab
2021-07-26 14:29     ` Carlos O'Donell
2021-07-26 14:32       ` H.J. Lu

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=4b8bcc59-362a-21ac-b531-6be07d0c722a@redhat.com \
    --to=carlos@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).