On 3/9/2018 6:49 PM, Daniel Ruggeri wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this candidate
tarball as 2.4.32:
[+1]: So far, so good
On 2018/03/10 02:49:15, "Daniel Ruggeri" <drugg...@primary.net> wrote:
> Hi, all;
>Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the next few days to r
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this candidate
tarball as 2.4.32:
[ ] +1: It's not just good, it's good enough!
[ ] +0: Let's have a talk
+1... The whole idea is to find bugs and issues before
we do a formal release. We found one. It may have been
"minor" but releasing s/w with known bugs is not something
we should do. We release code when it's ready.
> On Mar 7, 2018, at 9:52 AM, Daniel Ruggeri <drugg...@pr
On 07 Mar 2018, at 4:52 PM, Daniel Ruggeri <drugg...@primary.net> wrote:
> I tend to agree in principle. At the same time, we've discussed here that
> version numbers are cheap and that we generally would like to release more
> often, so I wanted to 'walk the talk'. Thank you for
On 2018-03-05 10:31, Joe Orton wrote:
On Sat, Mar 03, 2018 at 09:56:50AM -0600, Daniel Ruggeri wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release
On Sat, Mar 03, 2018 at 09:56:50AM -0600, Daniel Ruggeri wrote:
> Hi, all;
>
>Please find below the proposed release tarball and signatures:
>
> https://dist.apache.org/repos/dist/dev/httpd/
>
>
>
> I would like to call a VOTE over the next few days to relea
On Mon, Mar 5, 2018 at 3:16 AM, Daniel Ruggeri wrote:
>
>> -Original Message-
>> From: Yann Ylavic [mailto:ylavic@gmail.com]
>> Sent: Sunday, March 04, 2018 5:09 PM
[]
>> In this case though, this is not exactly "100% failure" in any
>> circonstances, for
> -Original Message-
> From: Yann Ylavic [mailto:ylavic@gmail.com]
> Sent: Sunday, March 04, 2018 5:09 PM
> To: httpd-dev <dev@httpd.apache.org>
> Subject: Re: Fix for ab defect (was: [VOTE] Release httpd-2.4.31)
>
> On Sun, Mar 4, 2018 at 11:4
On Sun, Mar 4, 2018 at 11:48 PM, Daniel Ruggeri wrote:
>
> I'd like to ask a followup question... how do we catch this in the
> test suite? With this (100% failure), ab still returns a 0 exit code.
> It *does* at least give the error message to STDERR. Perhaps we
> should
t: Sunday, March 04, 2018 1:25 PM
> To: li...@rhsoft.net
> Cc: httpd-dev <dev@httpd.apache.org>
> Subject: Fix for ab defect (was: [VOTE] Release httpd-2.4.31)
>
> On Sat, Mar 3, 2018 at 10:51 PM, Yann Ylavic <ylavic@gmail.com> wrote:
> > On Sat, Mar 3, 2018 at 6
@httpd.apache.org
Subject: [VOTE] Release httpd-2.4.31
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this candidate
tarball as 2.4.31:
[ ] +1: It's not just
On Sat, Mar 3, 2018 at 4:56 PM, Daniel Ruggeri <drugg...@primary.net> wrote:
>
> I would like to call a VOTE over the next few days to release this candidate
> tarball as 2.4.31:
[X] +1: It’s not just good, it’s good enough!
Works for me on Debian(s) 9, 8 and 7.
No opinion
On Sun, Mar 4, 2018 at 8:38 PM, li...@rhsoft.net wrote:
>
> Am 04.03.2018 um 20:33 schrieb Yann Ylavic:
>>
>> On Sun, Mar 4, 2018 at 8:27 PM, li...@rhsoft.net wrote:
>>>
>>>
>>> that patchfile is unuseable for rpmbuild
>>>
>>> + echo 'Patch #4
Am 04.03.2018 um 20:33 schrieb Yann Ylavic:
On Sun, Mar 4, 2018 at 8:27 PM, li...@rhsoft.net wrote:
that patchfile is unuseable for rpmbuild
+ echo 'Patch #4 (httpd-2.4.x-ab-nonblock_length.patch):'
Patch #4 (httpd-2.4.x-ab-nonblock_length.patch):
+ /usr/bin/patch
On Sun, Mar 4, 2018 at 8:27 PM, li...@rhsoft.net wrote:
>
> that pacthfile is unuseable for rpmbuild
>
> + echo 'Patch #4 (httpd-2.4.x-ab-nonblock_length.patch):'
> Patch #4 (httpd-2.4.x-ab-nonblock_length.patch):
> + /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=0
> can't
Am 04.03.2018 um 20:24 schrieb Yann Ylavic:
On Sat, Mar 3, 2018 at 10:51 PM, Yann Ylavic wrote:
On Sat, Mar 3, 2018 at 6:40 PM, li...@rhsoft.net wrote:
-1
"ab" no longer can benchmark https urls, same build-spec and environment
(Fedora 26 and 27)
On Sat, Mar 3, 2018 at 10:51 PM, Yann Ylavic wrote:
> On Sat, Mar 3, 2018 at 6:40 PM, li...@rhsoft.net wrote:
>>
>> -1
>>
>> "ab" no longer can benchmark https urls, same build-spec and environment
>> (Fedora 26 and 27)
>
> Hmm, looks like 2.4 is missing
> On Mar 3, 2018, at 4:51 PM, Yann Ylavic wrote:
>
> On Sat, Mar 3, 2018 at 6:40 PM, li...@rhsoft.net wrote:
>>
>> -1
>>
>> "ab" no longer can benchmark https urls, same build-spec and environment
>> (Fedora 26 and 27)
>
> Hmm, looks like 2.4 is
On Sat, Mar 3, 2018 at 6:40 PM, li...@rhsoft.net wrote:
>
> -1
>
> "ab" no longer can benchmark https urls, same build-spec and environment
> (Fedora 26 and 27)
Hmm, looks like 2.4 is missing http://svn.apache.org/r1580928 (second hunk).
This somehow never made it to 2.4.x,
Am 03.03.2018 um 16:56 schrieb Daniel Ruggeri:
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.31:
[ ] +1: It’s not just good, it’s
On Sat, Mar 3, 2018 at 10:00 AM, Daniel Gruno <humbed...@apache.org> wrote:
> On 03/03/2018 04:56 PM, Daniel Ruggeri wrote:
>> Hi, all;
>>
>>Please find below the proposed release tarball and signatures:
>>
>> https://dist.apache.org/repos/dist/dev/h
On 03/03/2018 04:56 PM, Daniel Ruggeri wrote:
> Hi, all;
>
> Please find below the proposed release tarball and signatures:
>
> https://dist.apache.org/repos/dist/dev/httpd/
I know this is a bit nitpicky, and we don't do this in all projects,
but...can we please have the
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this candidate
tarball as 2.4.31:
[ ] +1: It's not just good, it's good enough!
[ ] +0: Let's have
On Mon, Feb 26, 2018 at 11:46 AM, Joe Orton wrote:
> On Fri, Feb 23, 2018 at 09:23:50PM +0100, Yann Ylavic wrote:
>> Though this is the "else" (legacy) branch.
>>
>> $ pkg-config --list-all |grep ^lua
> ...
>> lua51 Lua - Lua language engine
>> lua52
All;
With the release issues identified during validation, we will call this vote
CLOSED with the statement that 2.4.30 is not suitable for public release. I
apologise for the clerical error in not noting this sooner.
On 2018/02/19 14:54:35, <drugg...@primary.net> wrote:
>
It likely makes sense to CLOSE this vote with the
result that 2.4.30 is not being released...
> On Feb 19, 2018, at 9:54 AM, drugg...@primary.net wrote:
>
> Hi, all;
>Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/h
On Fri, Feb 23, 2018 at 09:23:50PM +0100, Yann Ylavic wrote:
> Though this is the "else" (legacy) branch.
>
> $ pkg-config --list-all |grep ^lua
...
> lua51 Lua - Lua language engine
> lua52 Lua - Lua language engine
> lua5.2
On Fri, Feb 23, 2018 at 9:10 PM, Yann Ylavic wrote:
> On Fri, Feb 23, 2018 at 6:56 PM, Joe Orton wrote:
>> On Fri, Feb 23, 2018 at 10:04:30AM -0600, William A Rowe Jr wrote:
>>> Correct, as I said this may not be a regression, as it continues to locate
On Fri, Feb 23, 2018 at 6:56 PM, Joe Orton wrote:
> On Fri, Feb 23, 2018 at 10:04:30AM -0600, William A Rowe Jr wrote:
>> Correct, as I said this may not be a regression, as it continues to locate
>> /use/lib64 files.
>>
>> Modern ld is tolerant on linux at least when not in
On Fri, Feb 23, 2018 at 2:17 AM, Ruediger Pluem wrote:
> Hm, it work for me on Centos 6 and 7. What lua packages have you installed?
> I only have the 64 bit versions installed. Do you have 32 bit versions
> installed as well?
The delta between the first attempt after
On Fri, Feb 23, 2018 at 10:04:30AM -0600, William A Rowe Jr wrote:
> Correct, as I said this may not be a regression, as it continues to locate
> /use/lib64 files.
>
> Modern ld is tolerant on linux at least when not in -Wall more. Other archs
> may not be so kind.
r1825147 works for me on
Correct, as I said this may not be a regression, as it continues to locate
/use/lib64 files.
Modern ld is tolerant on linux at least when not in -Wall more. Other archs
may not be so kind.
On Feb 23, 2018 09:15, "Eric Covener" wrote:
>> Do you end up with an -L/usr/lib for
>> Do you end up with an -L/usr/lib for the module in your CentOS example?
>> Did it happen to pick up the lib64 path? Or no lib path at all?
>
> /usr/src/apache/httpd-2.4.x/srclib/apr/libtool --silent --mode=link gcc
> -std=gnu99 -pthread -Wall -O2 -g -o
> mod_lua.la -rpath
On 02/23/2018 03:43 PM, William A Rowe Jr wrote:
> On Fri, Feb 23, 2018 at 2:17 AM, Ruediger Pluem wrote:
>> Hm, it work for me on Centos 6 and 7. What lua packages have you installed?
>> I only have the 64 bit versions installed. Do you have 32 bit versions
>> installed as
On Fri, Feb 23, 2018 at 2:17 AM, Ruediger Pluem wrote:
> Hm, it work for me on Centos 6 and 7. What lua packages have you installed?
> I only have the 64 bit versions installed. Do you have 32 bit versions
> installed as well?
>
> On 02/22/2018 10:54 PM, William A Rowe Jr
Hm, it work for me on Centos 6 and 7. What lua packages have you installed?
I only have the 64 bit versions installed. Do you have 32 bit versions
installed as well?
On 02/22/2018 10:54 PM, William A Rowe Jr wrote:
> This wasn't pretty; candidate 2.4.30 build on current fedora...
>
>
; Hi, all;
>
>Please find below the proposed release tarball and signatures:
>
> https://dist.apache.org/repos/dist/dev/httpd/
>
>
>
> I would like to call a VOTE over the next few days to release this candidate
> tarball as 2.4.30:
>
>
>
> [ ] +1: It’s no
Wow! Nice work!
> Am 21.02.2018 um 21:34 schrieb Rainer Jung <rainer.j...@kippdata.de>:
>
> Am 19.02.2018 um 15:54 schrieb drugg...@primary.net:
>> Hi, all;
>>Please find below the proposed release tarball and signatures:
>> https://dist.apache.org/repo
he state of my AIX system I am still +1 on the release.
>>
>> - proxy/ssl.t almost totally fails with handhsake errors between
>> client and origin
>> [Tue Jun 13 21:37:04.265062 2017] [ssl:info] [pid 15073386:tid 6169]
>> SSL Library Error: error:14
Am 19.02.2018 um 15:54 schrieb drugg...@primary.net:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.30:
[ ] +1: It’s
On Tue, Jun 13, 2017 at 10:05 PM, Eric Covener <cove...@gmail.com> wrote:
> +1 AIX/xlc/ppc64
>
> I have two quirks to record, both are openssl / openssl 1.1 related
> but given the state of my AIX system I am still +1 on the release.
>
> - proxy/ssl.t almost totally fai
Am 19.02.2018 um 15:54 schrieb drugg...@primary.net:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.30:
[ ] +1: It’s
, <humbed...@apache.org> wrote:
> Author: humbedooh
> Date: Mon Feb 19 08:24:18 2018
> New Revision: 25136
>
> Log:
> Removing flood...
>
> Removed:
> release/httpd/flood/
>
On Tue, Feb 20, 2018 at 6:06 AM, Jim Jagielski <j...@jagunet.com> wrote:
> -1: I think with the release process hiccups and the Win issues
> noted in the "Current branche 2.4.30-dev issues" thread,
> we will need a 2.4.31. Additionally, there are some
> backpor
ache.org
>> Subject: Re: [VOTE] Release httpd-2.4.30
>>
>> Another thing that helps is providing some heads-up
>> that a T will actually be happening... Yeah, you
>> had noted the you were going to T on Monday
>> (in the "T of 2.4.30 Proposal" thread) b
> -Original Message-
> From: Jim Jagielski [mailto:j...@jagunet.com]
> Sent: Tuesday, February 20, 2018 6:10 AM
> To: dev@httpd.apache.org
> Subject: Re: [VOTE] Release httpd-2.4.30
>
> Another thing that helps is providing some heads-up
> that a T will actually b
iew=markup#l47
>>
>> It makes sense that the tag comes from a specific commit where the variable
>> was flipped... Should I adjust the script and retry?
>>
>> --
>> Daniel Ruggeri
>>
>> From: Jim Jagielski [mailto:j...@jagunet.com]
>> Sent: Mon
-1: I think with the release process hiccups and the Win issues
noted in the "Current branche 2.4.30-dev issues" thread,
we will need a 2.4.31. Additionally, there are some
backports in STATUS that could also be folded in.
> On Feb 19, 2018, at 9:54 AM, drugg...@primary.net wrote:
e.org/viewvc/httpd/httpd/tags/2.4.30/include/ap_release.h?view=markup#l47
>
> It makes sense that the tag comes from a specific commit where the variable
> was flipped... Should I adjust the script and retry?
>
> --
> Daniel Ruggeri
>
> From: Jim Jagielski [mailto
I adjust the script and retry?
--
Daniel Ruggeri
From: Jim Jagielski [mailto:j...@jagunet.com]
Sent: Monday, February 19, 2018 9:46 AM
To: dev@httpd.apache.org
Subject: Re: [VOTE] Release httpd-2.4.30
Hmmm... I'm not seeing the patch where AP_SERVER_DEVBUILD_BOOLEAN
in ap_release.h is set to 0
; in ap_release.h is set to 0
>>
>> How does your release process work? What we've always
>> done is make the req changes to the branch and then copy
>> from that branch to the tag. So the tag itself must refer to
>> a specific SVN number on the http-2.4 branch but I'm
On 19 Feb 2018, at 5:45 PM, Jim Jagielski <j...@jagunet.com> wrote:
> Hmmm... I'm not seeing the patch where AP_SERVER_DEVBUILD_BOOLEAN
> in ap_release.h is set to 0
>
> How does your release process work? What we've always
> done is make the req changes to the branch
Hmmm... I'm not seeing the patch where AP_SERVER_DEVBUILD_BOOLEAN
in ap_release.h is set to 0
How does your release process work? What we've always
done is make the req changes to the branch and then copy
from that branch to the tag. So the tag itself must refer to
a specific SVN number
> Am 19.02.2018 um 15:54 schrieb <drugg...@primary.net> <drugg...@primary.net>:
>
> Hi, all;
>Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the next f
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this candidate
tarball as 2.4.30:
[ ] +1: It's not just good, it's good enough!
[ ] +0: Let's have
.
Thanks for RM'ing!
Bill
On Nov 7, 2017 10:28 PM, "Daniel Ruggeri" <drugg...@primary.net> wrote:
> Hi, all;
>
>Please find the proposed 2.5.0-alpha release tarballs and signatures
> at the following location. This release candidate was tagged from trunk
e for
this build: http://people.apache.org/~druggeri/tmp/latest_sources.yml)
httpd:
vote:
version_info:
configure:
build:
result:
log:
test:
result:
log:
system:
kernel:
name:
release:
version:
machine:
libraries:
libxyz:
Feedback on anything else I sho
.
jacob.perk...@cpanel.net <mailto:jacob.perk...@cpanel.net>
Office: 713-529-0800 x 4046
Cell: 713-560-8655
> On Dec 11, 2017, at 3:42 AM, Stefan Eissing <stefan.eiss...@greenbytes.de>
> wrote:
>
> Daniel, I am very much interested in a smooth and more automated
> release
Daniel, I am very much interested in a smooth and more automated
release process. However, I am very unfamiliar regarding what is
all involved and cannot judge if it is complete. You'd probably
want Jim's input on this.
Cheers,
Stefan
> Am 09.12.2017 um 21:05 schrieb Daniel Ruggeri <
With about a month of time the vote has been running and just a single
+1 (my own), I'm of the opinion that this release has died on the vine.
I am sensitive to the fact that this is the holiday season, so I will
keep it open only a few more days so folks can pipe up if they are still
testing
: Linux
release: 3.16.0-4-amd64
version: #1 SMP Debian 3.16.39-1 (2016-12-30)
machine: x86_64
libraries:
openssl: "1.1.0g"
openldap: "2.4.45"
apr: "1.6.3"
apr-util: "1.6.1"
iconv: "1.2.2"
brotli: "1.0.1&qu
Yep, we had some discussions. Language was for me a problem to get my
wishes/issues to get understand. I had also language problems with others on
this list in the past. I mostly do not understand all when posted, and I am
not understood.
It was a pleasure to test mod_md on windows.
The
Disclaimer: Steffen and me got into each others hairs during the development
and testing of mod_md. I often have difficulties understanding what he means.
That led to frustrations on both sides, I suppose.
In the comment below, I find several things factually wrong, so I need to
answer.
> Am
nded Windows build support in trunk (yay!), I would
> really like us to include the Let's Encrypt Support in the next 2.4 release
> as an experimental mod_md plus the required and recommended changes to
> mod_ssl.
>
> Atm there is one blocker that prevents me from proposing
+1 from me!!
> On Nov 15, 2017, at 4:59 AM, Stefan Eissing <stefan.eiss...@greenbytes.de>
> wrote:
>
> Now that Gregg has landed Windows build support in trunk (yay!), I would
> really like us to include the Let's Encrypt Support in the next 2.4 release
> as an
On Wed, Nov 15, 2017 at 10:59 AM, Stefan Eissing
<stefan.eiss...@greenbytes.de> wrote:
> Now that Gregg has landed Windows build support in trunk (yay!), I
> would really like us to include the Let's Encrypt Support in the next
> 2.4 release as an experimental mod_md pl
Now that Gregg has landed Windows build support in trunk (yay!), I would really
like us to include the Let's Encrypt Support in the next 2.4 release as an
experimental mod_md plus the required and recommended changes to mod_ssl.
Atm there is one blocker that prevents me from proposing mod_ssl
On Sun, Nov 12, 2017 at 5:11 PM, Eric Covener wrote:
>> Below is an addition to the first message: It appears (from the -bloadmap
>> output) that XML_Parse is suppossed to be coming from apr-util. Or is it
>> APR-UTIL is the caller?
>>
>> :g/XML_Parse/p
>> (ld): keep XML_Parse
> Below is an addition to the first message: It appears (from the -bloadmap
> output) that XML_Parse is suppossed to be coming from apr-util. Or is it
> APR-UTIL is the caller?
>
> :g/XML_Parse/p
> (ld): keep XML_Parse
> ld: 0711-301 WARNING: Symbol specified with the -u flag not defined:
>
On 07/11/2017 17:21, Jan Ehrhardt wrote:
Steffen in gmane.comp.apache.devel (Thu, 19 Oct 2017 23:15:32 +0200):
I said before: In Apache.dsw is now project xml removed, it is not
building out of the box with current released apr-util. With coming
apr-util 1.6.1 it should be possible to build.
Steffen in gmane.comp.apache.devel (Thu, 19 Oct 2017 23:15:32 +0200):
>I said before: In Apache.dsw is now project xml removed, it is not
>building out of the box with current released apr-util. With coming
>apr-util 1.6.1 it should be possible to build.
>
>With the expat/xml changes in
is automatic, as is www.apache.org/dist/httpd from the
https://dist.apache.org/repos/dist/release/httpd).
> * I created two scripts[2] to automate the tagging of SVN and minor file
> modifications associated with a release as well as the push of the
> tarballs/signatures to the repo mirror. Unfortunat
> Till now I was assuming that we should get a trunk and a 2.5.0-alfa repo.
No, not expected yet.
25 #include "h2_proxy_util.h"
2.5.0-alfa:
23 #include "mod_proxy_http2.h"
24 #include "h2.h" <==
25 #include "h2_proxy_util.h
On Wednesday 08/11/2017 at 05:28, Daniel Ruggeri wrote:
Hi, all;
Please find the proposed 2.5.0-alpha release ta
Hi, all;
Please find the proposed 2.5.0-alpha release tarballs and signatures
at the following location. This release candidate was tagged from trunk
as of r1814469:
https://dist.apache.org/repos/dist/dev/httpd/
I'd like to call a vote to release this alpha candidate. Please do note
Steffen in gmane.comp.apache.devel (Thu, 19 Oct 2017 23:15:32 +0200):
>I said before: In Apache.dsw is now project xml removed, it is not
>building out of the box with current released apr-util. With coming
>apr-util 1.6.1 it should be possible to build.
>
>With the expat/xml changes in
> On 2 Nov 2017, at 10:51, Daniel Ruggeri <drugg...@primary.net> wrote:
>
> Hi, all;
>
>I know we've chatted about this somewhat in the past so I wanted to
> kick off a formal topic to see if we can establish consensus for a
> release cadence of httpd. As a
Hi, all;
I know we've chatted about this somewhat in the past so I wanted to
kick off a formal topic to see if we can establish consensus for a
release cadence of httpd. As a strawman proposal, I'd like to suggest
that we...
* Ensure stable branches are always in a releasable state (I
Will more than the required 3 +1 (binding) votes and some other
unbinding +1 votes, and no -1s, I call this vote not only CLOSED but
also PASSED.
Thx to all!
Well I got it now thanks mostly to your instructions Steefen, took
awhile but once I put the the pieces together I see what needs to be done.
On 10/20/2017 1:44 AM, Steffen wrote:
Nope, just double clicking Apache.dsw does now not create the xml
solution. And without xml solution httpd
Nope, just double clicking Apache.dsw does now not create the xml
solution. And without xml solution httpd does not build (httpd
regression).
When I revert the Apache.dsw changes all fine, no headache and is not
complicated at all here.
I do not care where expat is located.
And cmake
On 10/19/2017 5:49 PM, William A Rowe Jr wrote:
On Thu, Oct 19, 2017 at 4:15 PM, Steffen wrote:
I said before: In Apache.dsw is now project xml removed, it is not building
out of the box with current released apr-util. With coming apr-util 1.6.1 it
should be possible
On Thu, Oct 19, 2017 at 4:15 PM, Steffen wrote:
> I said before: In Apache.dsw is now project xml removed, it is not building
> out of the box with current released apr-util. With coming apr-util 1.6.1 it
> should be possible to build.
>
> With the expat/xml changes in
; geschreven:
>
> The pre-release test tarballs for Apache httpd
> version 2.4.29 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.29 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ]
.net>
Office: 713-529-0800 x 4046
Cell: 713-560-8655
> On Oct 17, 2017, at 2:00 PM, Jim Jagielski <j...@jagunet.com> wrote:
>
> The pre-release test tarballs for Apache httpd
> version 2.4.29 can be found at the usual place:
>
> http://httpd.apache.org/dev/
On Tue, Oct 17, 2017 at 03:00:36PM -0400, Jim Jagielski wrote:
> The pre-release test tarballs for Apache httpd
> version 2.4.29 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.29 GA.
On 18/10/2017 05:00, Jim Jagielski wrote:
> The pre-release test tarballs for Apache httpd
> version 2.4.29 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.29 GA.
>
> [ ] +1: Good to g
And a +1 report from Bernard Spil , who just built with
libressl on debian.
> Am 18.10.2017 um 11:06 schrieb Stefan Eissing <stefan.eiss...@greenbytes.de>:
>
>
>
>> Am 17.10.2017 um 21:00 schrieb Jim Jagielski <j...@jagunet.com>:
>>
>> The
> Am 17.10.2017 um 21:00 schrieb Jim Jagielski <j...@jagunet.com>:
>
> The pre-release test tarballs for Apache httpd
> version 2.4.29 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apach
On Tue, Oct 17, 2017 at 03:00:36PM -0400, Jim Jagielski wrote:
> The pre-release test tarballs for Apache httpd
> version 2.4.29 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.29 GA
The pre-release test tarballs for Apache httpd
version 2.4.29 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.29 GA.
[ ] +1: Good to go
[ ] +0: meh
[ ] -1: Danger Will Robinson. And why.
Vote will last
Datum: Thu, 5 Oct 2017 13:49:10 -0500
> Von:William A Rowe Jr <wr...@apache.org>
> An: annou...@httpd.apache.org
>
>
>
> Apache HTTP Server 2.4.28 Released
>
> October 5, 2017
>
> The Apache Software Foundation and the Apache HTTP S
roject
are pleased to announce the release of version 2.4.28 of the Apache
HTTP Server ("Apache"). This version of Apache is our latest GA
release of the new generation 2.4.x branch of Apache HTTPD and
represents fifteen years of innovation by the project, and is
recommended over all p
Hrm... looks like it was already announced? At least the
website sez it was, and it looks like an Email was
sent to announce@a.o but I'm not seeing anything on
the httpd lists.
FYI: I'll be announcing tomorrow
Sorry I ran out of cycles to jump on this on the 4th, and didn't see anyone
step up,
so I went ahead and still pushed it out a day late/day early this
afternoon. Hope you
had a worthwhile conference. Please help me double check any errors or
omissions,
I think it was already staged correctly.
Sure. Anyone who wants to announce, please do so!! :)
> On Oct 3, 2017, at 11:47 AM, William A Rowe Jr wrote:
>
> On Tue, Oct 3, 2017 at 6:46 AM, Jim Jagielski wrote:
>> With more than the required 3 +1 (binding) votes, and no
>> vetos, I call this vote
gt; wrote:
>
> The pre-release test tarballs for Apache httpd
> version 2.4.28 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.28 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1
On Thu, Sep 28, 2017 at 7:44 AM, Stefan Eissing
wrote:
> Update: disregard the man behind the curtain - for now.
>
> I have the strangest effects on my main machine under native macOS 10.12.6,
> which
> do not happen on my parallels ubuntu image and my laptop with
901 - 1000 of 4444 matches
Mail list logo