httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: Status for 2.4.20
Date Wed, 23 Mar 2016 12:27:41 GMT

> On Mar 23, 2016, at 7:58 AM, Noel Butler <> wrote:
> On 23/03/2016 20:56, Jim Jagielski wrote:
>> Let's see: I recalled the vote for 2.4.19 because of a
>> single issue, basically related to a missing few lines in
>> a file which prevented building on Win. Nice, easy, simple
>> fix.
>> Now it appears that a slew of "fixes" related to Win have
>> been applied which, according to some, makes the whole build-
>> on-Win situation much much worse.
>> Now I have no idea what the status of HEAD for 2.4 is and,
>> as a result, we are delaying the T&R and eventual release of
>> 2.4.19/20. All because a 4-line fix turned into a master-refactor
>> at the last minute.
>> I am tempted to revert 2.4 back...
> as stated previously, this shit will happen when certain people push with a release often
> AFAIK there is *ZERO* critical exploit bugs to be patched by any pending release, so
lets get house in order  S T A B L E , then worry about releases, jesus christ, we are not
ubuntu or redhat with set programs to release every 3 or 6 months regardless if shit is ready
or not.....
> flame away... IDGAF

I see your point and have no intent or desire to flame.

Release Often is hardly a Bad Thing, at least IMHO. When the
time is right for a release, then we release. It seemed a
good time, again IMHO.

My opinion that "this shit will happen" when, despite lots of
notice of intent to tag, and reminders to test, etc.. people
simply DON'T, wait for the test tarball, find breakage, and
then apply major restructure/refactor "at the last minute".

Sure, stuff that like occasionally will happen, and it is,
after all, why we create test tarballs and call for a vote.
But when it becomes the rule instead of the exception, then
we have an issue w/ the process and the workflow.

Frequent release, IMHO, are an indication of health and
project vitality. When Apache httpd is suffering from the
FUD of being old, slow, behind-the-times, lacking features
and capability, etc, I think showing our community that we
are actively working the code, adding features, fixing
bugs, making improvements, etc is a Good Thing.
View raw message