Release branch maintenance - Was: glibc 2.19 status?

[Mike Frysinger]

On Tuesday, February 04, 2014 21:08:55 Allan McRae wrote:
> 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.

it would mean bypassing the branch manager to a degree.  for the most part, 
distros are only backporting simple fixes, but that isn't true for all of 
them.  sometimes people do wholesale backports of things that don't belong 
(RedHat's comes to mind).  we could be more proactive though when we cherry 
pick back something with dropping a note to the list for branch inclusion.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20140204/b13e9ef9/attachment.sig>