public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Chung-Lin Tang <cltang@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>,
	libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Upcoming glibc 2.33 freeze in 2 weeks.
Date: Sun, 3 Jan 2021 19:36:36 +0800	[thread overview]
Message-ID: <490be674-b882-9dfd-ffc9-4bbc2b15a8b1@codesourcery.com> (raw)
In-Reply-To: <03617ab6-e0c9-34c0-827e-b654f7b7b2de@redhat.com>



On 2020/12/22 11:54 PM, Carlos O'Donell via Libc-alpha wrote:
> This is reminder that the development branch will freeze in
> approximately 2 weeks.
> 
> After that point you will need to discuss inclusion with
> Adhemerval Zanella, who has kindly volunteered to be the
> release manager for 2.33.
> 
> All of January is dedicated to stabilizing development with
> bug fixes and corrections to any ABIs that are currently
> committed.
> 
> The next public patch review meeting is on January 4th 2021
> and my focus will be on patches that need review for the
> release.
> 

I have added my patches for fixing the #17645 DSO sorting algorithm issues as blocker.

I'm not sure if they're important enough, but this patch has almost gotten approval
but was deemed too late in the release cycle, twice in the past year I think.
Hope it gets through this time.

Thanks,
Chung-Lin

  parent reply	other threads:[~2021-01-03 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 15:54 Carlos O'Donell
2020-12-28 21:32 ` Jim Wilson
2020-12-28 21:46   ` Adhemerval Zanella
2021-01-03 11:36 ` Chung-Lin Tang [this message]
2021-01-03 13:12   ` Carlos O'Donell
     [not found] <c445ecd9-6eb9-6136-3f26-c327c559cf2e () redhat ! com>
2021-01-03 20:43 ` Romain GEISSLER

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=490be674-b882-9dfd-ffc9-4bbc2b15a8b1@codesourcery.com \
    --to=cltang@codesourcery.com \
    --cc=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).