From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Closing branch release/2.27/master?
Date: Sat, 20 Apr 2024 10:16:57 +0300 [thread overview]
Message-ID: <20240420071657.GA11456@altlinux.org> (raw)
In-Reply-To: <9ef4b098-1513-44bc-b556-ade0a73ba02f@redhat.com>
On Wed, Apr 17, 2024 at 10:20:24AM -0400, Carlos O'Donell wrote:
> On 4/15/24 17:39, Dmitry V. Levin wrote:
> > Hi,
> >
> > On Mon, Apr 15, 2024 at 03:01:23PM -0400, Carlos O'Donell wrote:
> >> Dmitry,
> >>
> >> I was trying to close out branches that we likely no longer want
> >> to support and I noticed ALT p9 went EOL in 2023-12.
> >>
> >> Should we close release/2.27/master for support?
> >>
> >> Shall we remove "Release/2.27 by Dmitry V. Levin?"
> >> https://sourceware.org/glibc/wiki/Release/
> >
> > Given that I haven't backported anything to release/2.27/master for quite
> > some time and it's unlikely that somebody else would step in, it would be
> > fair to admit that 2.27 branch is no longer supported, so I updated the
> > wiki page accordingly.
>
> Thank you!
>
> I expect that ALT p10 will continue to use glibc 2.32, so I think we should keep that
> branch open and accepting security and bug fixes.
>
> Would ALT p10 ever rebase glibc to a newer version?
I'd say that kind of rebase is very unlikely.
--
ldv
prev parent reply other threads:[~2024-04-20 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 19:01 Carlos O'Donell
2024-04-15 21:39 ` Dmitry V. Levin
2024-04-17 14:20 ` Carlos O'Donell
2024-04-20 7:16 ` Dmitry V. Levin [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=20240420071657.GA11456@altlinux.org \
--to=ldv@altlinux.org \
--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).