[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3.4 and bug reports
From: |
Jordi Gutiérrez Hermoso |
Subject: |
Re: 3.4 and bug reports |
Date: |
Wed, 9 Feb 2011 23:10:44 -0600 |
2011/2/9 John W. Eaton <address@hidden>:
> On 9-Feb-2011, Jordi Gutiérrez Hermoso wrote:
>
> | On the topic of 3.4 bugs, can we actually patch on the 3.4 branch and
> | then merge that branch periodically with default in order to pull the
> | patch into default as well?
>
> In that case, who decides whether a patch is appropriate for the
> release branch? I'd prefer to be relatively conservative with that,
> so I'm not sure I want everyone making changes there.
The release manager would, because he would keep a separate sanctified
repo and would decide if and when to pull the 3.4 patches we make.
Everyone can propose a patch there, but only the release manager
decides to pull it. If we all had our private repos public, this could
be a bit easier. Maybe this sounds awkward, though?
> | It would eliminate the problem of having
> | duplicated transplanted patches on default and stable,
>
> How is this a problem for you, if you are not the one who is managing
> the process of transplanting patches?
It introduces some weirdness in history and statistics. Now that I'm
working on the codeswarm, it's introduced a bit of noise, since some
people seem doubly active, although if their patches went into 3.4,
perhaps they deserve it. I know this sounds frivolous, but it could
also reduce work for the release manager, all he has to do is pull and
push, not transplant.
- Jordi G. H.