httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: [VOTE] The 'RM' Baton
Date Wed, 10 Jul 2013 13:22:06 GMT
Considering that I've been the only RM for 2.4.x, I can't help but
assume that Bill is referring to me.

As mentioned by others, by indicating a desire to T&R, it energizes
people to catch up on STATUS, place their votes and propose backports.
So it is *expected* that at a time when things should be the most
"stable" (right before a "release"), that there is a flurry of
activity. So what if it means a delay of a few weeks or even a month.
The result is a *better* release for our users, which I think is
even more important.

Sure it would be nice to have releases more often, but that is due,
IMO at least, to the difficulty in getting 3 +1 votes on anything
but the most trivial of backports...

I'm not gonna mention the irony of this whole proposal coming from
the person it is coming from...

On Jul 10, 2013, at 8:13 AM, Eric Covener <> wrote:

> I think the problem with no-one picking up the baton on a stalled
> release is just a different angle on the same participation problem --
> what little resource there is gobbled up by non-RM activities (some of
> it self imposed overhead as you outlined in the other thread).
> So my concern with the proposal  -- are there really wiling/able RM's
> waiting in the wings in these periods?  If they're there -- are they
> afraid of stepping on an RM's toes, or of drawing a line in the sane
> for the half-approved backports?
> (I have personally never RM'ed. To me it's intimidating and unknown
> and with a log of competing work it's hard to step up and tackle.
> Maybe we should make it make a condition of PMC membership at least
> once per decade?)

View raw message