Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Jim Jagielski]

I am recalling this VOTE as well.

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Jim Jagielski]

> On Jun 21, 2016, at 10:58 AM, William A Rowe Jr  wrote:
> 
> 
>  
> > On Jun 21, 2016, at 7:39 AM, Jim Jagielski  wrote:
> >
> > Just a reminder for those still testing and/or waiting to cast
> > a vote: One cannot veto a release and even tho OtherBill has
> > voted a someway bi-polar -1, my intent is to, assuming the required
> > 3 or more (binding) +1s, release this despite the diatribe
> > below.
> 
> My mental state, really, Jim? Well, now you know why I sat on the
> fence deciding whether to not vote, and let you eat the eggs of the
> users affected, or vote -1. It took until you re-rolled without any
> feedback for me to get off the fence in defense of those users who
> are adversely impacted by your short-sightedness.
> 

bi-polar *obviously* referred to the *vote*, as syntax and grammar
make clear.

> 
> >>
> >> Given the lengths Jens Schleusener needed to go through to diagnose
> >> this during the original release candidate vote, and the availability of
> >> the patch prior to this tag to fix the RM's own defect (demonstrated
> >> easily with any --enable-modules of few or none, after this community
> >> went to great lengths to re-think the appropriate categorization of all
> >> modules under all/most/few schema) this candidate is clearly not
> >> ready for prime time.
> >>
> >> In all other respects, I see no significant regressions or new issues.
> >> Thanks for RM'ing (2x now)!
> >>
> >>
> >
> 
> 

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Stefan Eissing]

In an ideal world, we'd have test cases for each bug ever found. 
In an ideal world, we'd only call something a regression when we have  a test 
case for it.
In an ideal world, we'd have tireless testers with infinite time to get things 
right.
In an ideal world, we do not have to compromise.

In the real world, we will always have bugs in every release.
In the real world, we should never release something which shows bugs in our 
test suite.
In the real world, if we find bugs without test coverage, we have to weigh 
things.
In the real world, manual tests do not improve on the n-th iteration, as people 
get bored/tired/don't have the time.

In this case, we know of a bug, but have no test case for it.
In this case, it used to work before, but no longer.
In this case, it is not affecting users of the built server.
In this case, there are workarounds for people building httpd (which is a much 
smaller number than users).

Therefore, I vote

+1

on releasing 2.4.22.

PS. I would appreciate if we could pour some of the energy visible here into 
having a build server that just runs some build configurations nightly/weekly. 
2.4.19 failed because of Windows issues, 2.4.22 has hick ups as of build 
configuration issues. Only automation will improve things for the releases to 
come.

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[William A Rowe Jr]

On Tue, Jun 21, 2016 at 7:21 AM, Jim Jagielski  wrote:

> Unless, of course, it hits/affects a lot more people
> and such a build environment which triggers the bug it
> much more common than currently envisioned. Since this
> issue exists in trunk as well, and has for a long while,
> this is somewhat doubtful, but I have provided a small
> tweet encouraging a larger group of people to test it
> out.


/boggle

Twitter is now representative of our user community?
Why not ask users@ if that's whom you sought to poll?

Trunk... https://w3techs.com/technologies/details/ws-apache/2/all
widely adopted by less than .1% of 52% of sites sampled.
That hardly seems representative.

You can directly count the number of responses to the 'please
test 2.4.21' thread to come up with a much larger number than
.05% of testers who tripped over and wasted some not-insignificant
time troubleshooting and reporting the bug, a report you ignored
related to your own config code and backport. Not exactly a
classy move.


> > On Jun 21, 2016, at 7:39 AM, Jim Jagielski  wrote:
> >
> > Just a reminder for those still testing and/or waiting to cast
> > a vote: One cannot veto a release and even tho OtherBill has
> > voted a someway bi-polar -1, my intent is to, assuming the required
> > 3 or more (binding) +1s, release this despite the diatribe
> > below.
>

My mental state, really, Jim? Well, now you know why I sat on the
fence deciding whether to not vote, and let you eat the eggs of the
users affected, or vote -1. It took until you re-rolled without any
feedback for me to get off the fence in defense of those users who
are adversely impacted by your short-sightedness.

If you want to treat 2.4.x as a perpetual beta, it will be in spite of
my -1 votes for all regressions we can collectively uncover. At least
the mod_http2 was in fact clearly tagged experimental... running
./configure is not.


> >> On Jun 20, 2016, at 10:35 PM, William A Rowe Jr 
> wrote:
> >>
> >> On Mon, Jun 20, 2016 at 8:20 AM, Jim Jagielski  wrote:
> >> The pre-release test tarballs for Apache httpd 2.4.22 can be found
> >> at the usual place:
> >>
> >>http://httpd.apache.org/dev/dist/
> >>
> >> I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.
> >>
> >> [ ] +1: Good to go
> >> [ ] +0: meh
> >> [X] -1: Danger Will Robinson. And why.
> >>
> >> Given the lengths Jens Schleusener needed to go through to diagnose
> >> this during the original release candidate vote, and the availability of
> >> the patch prior to this tag to fix the RM's own defect (demonstrated
> >> easily with any --enable-modules of few or none, after this community
> >> went to great lengths to re-think the appropriate categorization of all
> >> modules under all/most/few schema) this candidate is clearly not
> >> ready for prime time.
> >>
> >> In all other respects, I see no significant regressions or new issues.
> >> Thanks for RM'ing (2x now)!
> >>
> >>
> >
>
>

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Jim Jagielski]

Unless, of course, it hits/affects a lot more people
and such a build environment which triggers the bug it
much more common than currently envisioned. Since this
issue exists in trunk as well, and has for a long while,
this is somewhat doubtful, but I have provided a small
tweet encouraging a larger group of people to test it
out.

> On Jun 21, 2016, at 7:39 AM, Jim Jagielski  wrote:
> 
> Just a reminder for those still testing and/or waiting to cast
> a vote: One cannot veto a release and even tho OtherBill has
> voted a someway bi-polar -1, my intent is to, assuming the required
> 3 or more (binding) +1s, release this despite the diatribe
> below.
> 
>> On Jun 20, 2016, at 10:35 PM, William A Rowe Jr  wrote:
>> 
>> On Mon, Jun 20, 2016 at 8:20 AM, Jim Jagielski  wrote:
>> The pre-release test tarballs for Apache httpd 2.4.22 can be found
>> at the usual place:
>> 
>>http://httpd.apache.org/dev/dist/
>> 
>> I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.
>> 
>> [ ] +1: Good to go
>> [ ] +0: meh
>> [X] -1: Danger Will Robinson. And why.
>> 
>> Given the lengths Jens Schleusener needed to go through to diagnose 
>> this during the original release candidate vote, and the availability of 
>> the patch prior to this tag to fix the RM's own defect (demonstrated 
>> easily with any --enable-modules of few or none, after this community 
>> went to great lengths to re-think the appropriate categorization of all 
>> modules under all/most/few schema) this candidate is clearly not 
>> ready for prime time.
>> 
>> In all other respects, I see no significant regressions or new issues.
>> Thanks for RM'ing (2x now)!
>> 
>> 
> 

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Jim Jagielski]

Just a reminder for those still testing and/or waiting to cast
a vote: One cannot veto a release and even tho OtherBill has
voted a someway bi-polar -1, my intent is to, assuming the required
3 or more (binding) +1s, release this despite the diatribe
below.

> On Jun 20, 2016, at 10:35 PM, William A Rowe Jr  wrote:
> 
> On Mon, Jun 20, 2016 at 8:20 AM, Jim Jagielski  wrote:
> The pre-release test tarballs for Apache httpd 2.4.22 can be found
> at the usual place:
> 
> http://httpd.apache.org/dev/dist/
> 
> I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.
> 
> [ ] +1: Good to go
> [ ] +0: meh
> [X] -1: Danger Will Robinson. And why.
> 
> Given the lengths Jens Schleusener needed to go through to diagnose 
> this during the original release candidate vote, and the availability of 
> the patch prior to this tag to fix the RM's own defect (demonstrated 
> easily with any --enable-modules of few or none, after this community 
> went to great lengths to re-think the appropriate categorization of all 
> modules under all/most/few schema) this candidate is clearly not 
> ready for prime time.
> 
> In all other respects, I see no significant regressions or new issues.
> Thanks for RM'ing (2x now)!
> 
> 

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[William A Rowe Jr]

On Mon, Jun 20, 2016 at 8:20 AM, Jim Jagielski  wrote:

> The pre-release test tarballs for Apache httpd 2.4.22 can be found
> at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [X] -1: Danger Will Robinson. And why.
>

Given the lengths Jens Schleusener needed to go through to diagnose
this during the original release candidate vote, and the availability of
the patch prior to this tag to fix the RM's own defect (demonstrated
easily with any --enable-modules of few or none, after this community
went to great lengths to re-think the appropriate categorization of all
modules under all/most/few schema) this candidate is clearly not
ready for prime time.

In all other respects, I see no significant regressions or new issues.
Thanks for RM'ing (2x now)!

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Reindl Harald]

Am 20.06.2016 um 15:20 schrieb Jim Jagielski:

The pre-release test tarballs for Apache httpd 2.4.22 can be found
at the usual place:

http://httpd.apache.org/dev/dist/

I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.

[x] +1: Good to go
[ ] +0: meh
[ ] -1: Danger Will Robinson. And why


+1

looks good on Fedora 23 x86_64



signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Jan Ehrhardt]

Jim Jagielski in gmane.comp.apache.devel (Mon, 20 Jun 2016 09:20:43
-0400):
>The pre-release test tarballs for Apache httpd 2.4.22 can be found
>at the usual place:
>
>   http://httpd.apache.org/dev/dist/
>
>I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.
>
>[ ] +1: Good to go

Running on a Windows 2008R2 server now, built with VC9 x86. OpenSSl 1.0.2h
Fips, mod_http2.
-- 
Jan

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Stefan Eissing]

> Am 20.06.2016 um 15:20 schrieb Jim Jagielski :
> 
> The pre-release test tarballs for Apache httpd 2.4.22 can be found
> at the usual place:
> 
>   http://httpd.apache.org/dev/dist/
> 
> I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.
> 
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
> 
> Vote will last the normal 72 hrs.
> 
> NOTE: The *-deps are only there for convenience.
> 
> Thx!

Tested:
* 14.04.1-Ubuntu, x86_64

Re: [VOTE] Release Apache httpd 2.4.22 as GA

[Jim Jagielski]

> On Jun 20, 2016, at 9:20 AM, Jim Jagielski  wrote:
> 
> The pre-release test tarballs for Apache httpd 2.4.22 can be found
> at the usual place:
> 
>   http://httpd.apache.org/dev/dist/
> 
> I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.
> 
> [X] +1: Good to go

Tested:
 o CentOS6, x64
 o CentOS7, x64
 o OSX 10.11.5 / Xcode 7.3.1, x64

[VOTE] Release Apache httpd 2.4.22 as GA

[Jim Jagielski]

The pre-release test tarballs for Apache httpd 2.4.22 can be found
at the usual place:

http://httpd.apache.org/dev/dist/

I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA.

[ ] +1: Good to go
[ ] +0: meh
[ ] -1: Danger Will Robinson. And why.

Vote will last the normal 72 hrs.

NOTE: The *-deps are only there for convenience.

Thx!