> -----Original Message----- > From: Daniel Ruggeri <drugg...@apache.org> > Sent: Tuesday, March 13, 2018 12:00 PM > To: dev@httpd.apache.org > Subject: [RESULT] [VOTE] Release httpd-2.4.32 > > Hi, all; > > 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 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: There's trouble in paradise. Here's what's wrong. > > > > > > > > The computed digests of the tarball up for vote are: > > > > md5: cddf45e036657ea209145169a554bbff *httpd-2.4.32.tar.gz > > > > sha1: fc1f26a4d302639932332ea12b40de7503f8aab0 *httpd-2.4.32.tar.gz > > > > sha256: > 11cd0c43135ffe89706d0558abc0d19cb4a1f203e11ada52f2e1c3f790959300 > > *httpd-2.4.32.tar.gz > > > > > > > > -- > > > > Daniel Ruggeri > > I am pleased to report that the vote for releasing httpd-2.4.32 has PASSED > with five binding +1 votes. I will continue with the process to release and > distribute the tarball. Bear with me as I learn through the procedure :-) > > I do know that Announcement2.4.* and CHANGES_2.4 also require updates - > feel free to point out anything missing. > > -- > Daniel Ruggeri
Well, this is an interesting predicament indeed. A release has passed, but a regression was found after the fact... I volunteer to T&R 2.4.33 as soon as we're able to resolve this regression, but in any event, I am not comfortable sending the announcement that this represents the latest and best version at this point - especially given that we appear to have a patch for testing: https://lists.apache.org/thread.html/adc854d8b395367ede75f327c1324c088d00701 33d0c7f6931822d0e@%3Cdev.httpd.apache.org%3E So... that leaves me wondering how we would treat this. By now, most of the mirrors should have caught up with the new version, announcement text and CHANGES*. I did not update the CURRENT-IS-xxxx pointer yet, though. How do we treat this version in STATUS - as in... at what point does a release become a release? When it gets the votes? When it's pushed to dist/release? When the announcement is made? Personally, I would like to see *another* T&R (again, I volunteer and will see it through quickly) and no mention of this release be made public via ANNOUNCE. Thoughts? -- Daniel Ruggeri
