You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2013/07/10 20:03:53 UTC
[VOTE] Lazy Consensus for 2.4.x backports
Pulling this out as a proposal:
I propose that we track all backports in 2.4 STATUS as we currently
do. Each backport is time-tagged and we operate under a lazy
consensus. Assuming no -1 votes within 96 hours, the backport
can be applied to 2.4.x. If the backport gets 3 +1 votes sooner
than that, then it can be applied asap...
As with ALL patches, any commit can be reverted for good
technical (or legal) reasons.
[ ] +1: Agree with this proposal (to start post 2.4.5 release)
[ ] -1: Disagree with this proposal (and why)
Re: [VOTE] Lazy Consensus for 2.4.x backports
Posted by Jeff Trawick <tr...@gmail.com>.
On Wed, Jul 10, 2013 at 3:09 PM, Eric Covener <co...@gmail.com> wrote:
> > If I count right, 80% or more of the fixes potentially in 2.4.next are
> > already there (I didn't count mod_lua.) That doesn't seem so bad.
>
> FWIW, I had a flurry of trivial fixes in trunk that I didn't want to
> derail/delay 2.4.5 with, which inflates the remaining 20% a bit.
>
My set for "fixes potentially in 2.4.next" was
stuff still in 2.4.x/STATUS
stuff in 2.4.x/CHANGES other than mod_lua fixes
There's any number of reasons why something is in trunk but never proposed
for backport, so I didn't consider it. (IOW, it needs at least one
proponent to potentially be in a stable release.)
--
Born in Roswell... married an alien...
http://emptyhammock.com/
Re: [VOTE] Lazy Consensus for 2.4.x backports
Posted by Eric Covener <co...@gmail.com>.
> If I count right, 80% or more of the fixes potentially in 2.4.next are
> already there (I didn't count mod_lua.) That doesn't seem so bad.
FWIW, I had a flurry of trivial fixes in trunk that I didn't want to
derail/delay 2.4.5 with, which inflates the remaining 20% a bit.
RE: [VOTE] Lazy Consensus for 2.4.x backports
Posted by Plüm,
Rüdiger,
Vodafone Group <ru...@vodafone.com>.
> From: Jeff Trawick [Sent: Mittwoch, 10. Juli 2013 21:04
> To: Apache HTTP Server Development List
> Subject: Re: [VOTE] Lazy Consensus for 2.4.x backports
>
> On Wed, Jul 10, 2013 at 2:03 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> Pulling this out as a proposal:
>
> I propose that we track all backports in 2.4 STATUS as we currently
> do. Each backport is time-tagged and we operate under a lazy
> consensus. Assuming no -1 votes within 96 hours, the backport
> can be applied to 2.4.x. If the backport gets 3 +1 votes sooner
> than that, then it can be applied asap...
>
> As with ALL patches, any commit can be reverted for good
> technical (or legal) reasons.
>
> [ ] +1: Agree with this proposal (to start post 2.4.5 release)
> [ ] -1: Disagree with this proposal (and why)
>
> -1
>
> The current process
>
> * works well/appropriately IMO; to me that means pretty good stream of fixes to 2.4.x without too high a risk of regressions
> * has demonstrably resulted in a reasonably small number of regressions so far across 2.4.x and earlier releases (definitely not zero > regressions, but pretty darn low).
>
> I think that it is a safe assumption that there will be code changes in stable releases that have had less review if we make this
> change. Largely regression-free stable releases are of crucial importance for infrastructure software like httpd, more so than
> getting another window-size worth of fixes into the release, especially if they've been looked at less than the others.
>
> If I count right, 80% or more of the fixes potentially in 2.4.next are already there (I didn't count mod_lua.) That doesn't seem so
> bad.
Well put and I agree with this. So -1 from me as well.
Regards
Rüdiger
Re: [VOTE] Lazy Consensus for 2.4.x backports
Posted by Jeff Trawick <tr...@gmail.com>.
On Wed, Jul 10, 2013 at 2:03 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> Pulling this out as a proposal:
>
> I propose that we track all backports in 2.4 STATUS as we currently
> do. Each backport is time-tagged and we operate under a lazy
> consensus. Assuming no -1 votes within 96 hours, the backport
> can be applied to 2.4.x. If the backport gets 3 +1 votes sooner
> than that, then it can be applied asap...
>
> As with ALL patches, any commit can be reverted for good
> technical (or legal) reasons.
>
> [ ] +1: Agree with this proposal (to start post 2.4.5 release)
> [ ] -1: Disagree with this proposal (and why)
>
>
-1
The current process
* works well/appropriately IMO; to me that means pretty good stream of
fixes to 2.4.x without too high a risk of regressions
* has demonstrably resulted in a reasonably small number of regressions so
far across 2.4.x and earlier releases (definitely not zero regressions, but
pretty darn low).
I think that it is a safe assumption that there will be code changes in
stable releases that have had less review if we make this change. Largely
regression-free stable releases are of crucial importance for
infrastructure software like httpd, more so than getting another
window-size worth of fixes into the release, especially if they've been
looked at less than the others.
If I count right, 80% or more of the fixes potentially in 2.4.next are
already there (I didn't count mod_lua.) That doesn't seem so bad.
--
Born in Roswell... married an alien...
http://emptyhammock.com/
Re: [VOTE] Lazy Consensus for 2.4.x backports
Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On Wed, 10 Jul 2013 14:03:53 -0400
Jim Jagielski <ji...@jaguNET.com> wrote:
> Pulling this out as a proposal:
>
> I propose that we track all backports in 2.4 STATUS as we currently
> do. Each backport is time-tagged and we operate under a lazy
> consensus. Assuming no -1 votes within 96 hours, the backport
> can be applied to 2.4.x. If the backport gets 3 +1 votes sooner
> than that, then it can be applied asap...
>
> As with ALL patches, any commit can be reverted for good
> technical (or legal) reasons.
>
> [X] -1: Disagree with this proposal (and why)
Agreed in part, that *major* backports (or activity, if we did set
aside /trunk/ for the near-term) are tracked in STATUS with lazy
consensus. I actually thought the 72 hours was not a bad window.
I would think a +/-0 with discussion would be enough to add some
days for deeper consideration of a proposal.
Disagree in part, that minor backports (or activity, if we did set
aside /trunk/ for the near-term) do not need STATUS and should not
have the obstacle of STATUS tracking.