As mentioned before, I actually want to RM, but am still waiting for *any* confirmation that the dead-on-the-vine 2.6 release I bundled is at least structurally correct and matches project expectations. Since releases of source are one of the few things the version control time machine cannot undo (and are sacred things to the ASF as well), I want to be sure of the procedure. Maybe instead of doing the RM job, I could talk you into putting the (presumably less) volunteer time to vetting out the previous work so we can add to the number of folks willing and comfortable being RM?
Side note, the slotmem fix seems like a showstopper, right? I'd want to see that in before a T&R. -- Daniel Ruggeri On February 14, 2018 7:22:02 AM CST, Jim Jagielski <j...@jagunet.com> wrote: >I propose a T&R of 2.4.30 on Feb 19th. I offer to RM >unless someone else would like to do so.
