[Changing subject, don't mean to hijack the 2.4 activity train] There is a modestly important patch, already backported to 2.4.x branch, that is still sitting in 2.2 status. Could one more committer please review and vote on that remaining fix?
Because it helps to avert an unintended doubled response in some edge cases, I consider this one important enough to hold up 2.2 tag for some more hours. Bill On Tue, Jun 2, 2015 at 4:36 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote: > On Tue, Jun 2, 2015 at 6:32 AM, Jim Jagielski <j...@jagunet.com> wrote: > >> Although there are some cool things that I'd like to see in >> 2.4.13, I don't want to hold off any longer (plus, those >> cool things would be good incentive for a 2.4.14 sooner >> rather than later). >> >> I plan to T&R 2.4.13 on Thurs, by Noon eastern. >> > > +1, planning to match you with a T&R of 2.2.30 on the same timetable. > > There is a nominally important last patch in 2.2 STATUS, if a third pair > of eyes have the cycles to review it. >
