On Mon, 2013-09-16 at 11:10 +0200, Jakub Hrozek wrote:
On Fri, Sep 13, 2013 at 12:41:41PM -0400, Simo Sorce wrote:
> I wonder if it wouldn't make sense to delay commits to stable branches
> until the time to release comes ?
>
> Would it make it easier or harder to review and apply changes only at
> release time ?
>
> Simo.
>
> --
> Simo Sorce * Red Hat, Inc * New York
It *may* bring more stability, but as Sumit noted, at a cost.
Did you see any particular problem of a patch not well tested that went
into the master? Or was it a general concern about the memcache patches?
I was more thinking about cases where you may want to defer the decision
of backporting a patch to a branch. By selecting patches at one time you
'might' be able to see a larger picture and have a more focused release,
or change release direction at any point in time.
But no, so far I haven't seen a huge problem except for the need to keep
tabs on multiple branches at the same time.
btw how do larger projects (Samba?) handle this?
Our release manager backports bugs to the next stable tree only if there
is a bug that asks for it with a backport patch and acks from
developers. She does that at her own pace. After RC only critical bugs
are allowed in the stable branch before release.
Release management and development are quite separated in samba.
Simo.
--
Simo Sorce * Red Hat, Inc * New York