On Wed, Jun 3, 2009 at 11:18 PM, Roland McGrathrol...@redhat.com wrote:
I propose these as recommended guidelines for all release branch managers:
1. Don't talk about recommended guidelines for all release branch managers.
No, wait, do talk about them.
Don't suspect your neighbor.
On Wed, Jun 03, 2009 at 08:18:30PM -0700, Roland McGrath wrote:
I hereby solicit somebody to make sure the results of these discussions
get wikiized. Don't all fall over yourselves rushing to volunteer.
I can do it after it becomes clear whatever we reached is the final
consensus for now.
I
You've talked a lot about detailed concrete criteria for what to include
on a release branch and how to operate it. That's a lovely discussion,
but I think it may have a bit missed the point of what I'm trying to start.
With the special exception of copyright rules, the sum of what I intended
to
On Sun, 24 May 2009, Petr Baudis wrote:
Hi,
I added glibc maintainers of several major Linux distributions to Cc
list to gather their opinions on what kind of patches should be included
in the glibc-2.10-branch if they were to use that instead of the current
practice (the only release
On Sunday 24 May 2009 07:44:40 Petr Baudis wrote:
I'm full-quoting the mail. Summary of previous discussion: Me and
Roland agree that (up to exceptions) only cherry-picked commits from
master will appear on the branch, they will be only bugfixes and API/ABI
will never be changed. What we
Hi,
I added glibc maintainers of several major Linux distributions to Cc
list to gather their opinions on what kind of patches should be included
in the glibc-2.10-branch if they were to use that instead of the current
practice (the only release and variously large patchball of backported
6 matches
Mail list logo
