Note that the vote may run longer than 72 hours as 72 is the minimum. As it stands now, we have more than 3 binding +1 votes, but I am waiting for closure on the conversation on-list about the tests with reported H2/TLS 1.3 failures. Since this is one of the primary features of this release, I want to be sure the topic gets due attention.
On October 14, 2018 4:44:04 PM CDT, "Helmut K. C. Tessarek" <tessarek@xxxxxxxxxxx> wrote:
On 2018-10-10 15:18, Daniel Ruggeri wrote:
Please find below the proposed release tarball and signatures:
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.36:
[ ] +1: It's not just good, it's good enough!
[ ] +0: Let's have a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: e40e7a879b84df860215b8a80f2a535534a1c4b4 *httpd-2.4.36.tar.gz
72h have passed, so what is the outcome of the vote?