This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Proposal to revitalize release branches: Make them cheap, and make them work.
- From: Adam Conrad <adconrad at 0c3 dot net>
- To: Will Newton <will dot newton at linaro dot org>
- Cc: Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Roland McGrath <roland at hack dot frob dot com>, Allan McRae <allan at archlinux dot org>, David Miller <davem at davemloft dot net>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 3 Oct 2014 14:35:24 +0000
- Subject: Re: Proposal to revitalize release branches: Make them cheap, and make them work.
- Authentication-results: sourceware.org; auth=none
- References: <542DBB6F dot 6040109 at redhat dot com> <CANu=DmiR46wgA7vfmXUsbqsHdrjq9vMPLCLoJSGqGJSeKXWmCA at mail dot gmail dot com> <20141003142938 dot GU28005 at 0c3 dot net>
On Fri, Oct 03, 2014 at 08:29:38AM -0600, Adam Conrad wrote:
>
> With that change, the process for a stable branch cherrypick or backport
> is literally "commit locally, push, forget about it", which sounds like
> exactly how simple we need to make this to make those branches widely
> used.
Oh, one addendum to this. While I agree that posts to libc-stable should
be automatic for commits to the *stable* branches, I think it was also be
a nice habit to form that when you commit something to trunk that should
be backported, and don't want to take responsibility for that backport
yourself (which would generate the above automated commit mail), a CC to
libc-stable on your libc-alpha commit would be nice.
So, regular commits to trunk, no big deal, no extra work, but a trunk
commit of a critical bugfix or security-related patch, etc, you either
backport to a stable branch *or* CC:stable on your libc-alpha [committed]
message, so those following the stable list will spot it without having
to comb through libc-alpha.
... Adam