This is the mail archive of the
mailing list for the glibc project.
Re: Release branch maintenance - Was: glibc 2.19 status?
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Allan McRae <allan at archlinux dot org>
- Cc: Mike Frysinger <vapier at gentoo dot org>, libc-alpha at sourceware dot org, Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, Siddhesh Poyarekar <siddhesh at redhat dot com>, Alexandre Oliva <aoliva at redhat dot com>, Carlos O'Donell <carlos at redhat dot com>
- Date: Tue, 4 Feb 2014 09:57:30 -0800 (PST)
- Subject: Re: Release branch maintenance - Was: glibc 2.19 status?
- Authentication-results: sourceware.org; auth=none
- References: <52E649BF dot 5020400 at archlinux dot org> <CAAHN_R2r6jiHWwj2HGDS-sruGewKEMmeQkAS9PXqZtOS95gKAw at mail dot gmail dot com> <52EC58E6 dot 6060702 at archlinux dot org> <3673077 dot Nn8N4XpUPj at vapier> <52F0CA47 dot 8030205 at archlinux dot org>
> I suppose I was not very clear, but it was implied that only patches
> that have landed on master and are bug fixes are eligible for pulling to
> the release branch. My point was that whether distros consider it worth
> backporting for their package is a good indicator of the need to
> cherry-pick to the release branch.
The original definition of the release branch process was that it would get
whatever backport patches the consensus of distro maintainers plus the
release manager thought wise.