I am happy to T&R in the coming days. The approved mod_ssl EC patch has me a bit concerned that it is so out of sync with what has been proposed for back port to 2.4 - I spent some time reviewing that 2.4 patch as well and think it would be easier if the 2.4 patch were split into two proposals... those which will be adopted in 2.2 and features proposed exclusively for 2.4.
I am also concerned we keep 100-continue behavior in synch and pick up T-E/C-L corrections. Otherwise I concur that 2.2.26 needs to happen sooner rather than than later, largely as a bug fix release to recent regressions. There is no need to overload it with a fresh rush of feature backports. I am happy to RM a 2.2.27 in Jan for such maintenance. On Nov 8, 2013 11:45 AM, "Ben Reser" <b...@reser.org> wrote: > Does anyone have a timetable for a 2.2.26 release? > > Subversion users have been running into the issues introduced in 2.2.25 and > we've been pointing them at patches. Some but not all of the binaries > floating > around have been patched. It would be really nice to be able to have a > httpd > release to point them at. > > For instance this guy popped up yesterday: > > https://mail-archives.apache.org/mod_mbox/subversion-users/201311.mbox/%3C4A2A8BDDBE6EFE4199FB22121DB971B1A1B07E6B%40AAPLExchange.aapl.com.au%3E > > In the meantime I've posted this thread on the users@subversion.apache.orglist > in an effort to help users: > > https://mail-archives.apache.org/mod_mbox/subversion-users/201311.mbox/%3C527C7AC3.5050906%40reser.org%3E > > The PR 55306 and PR 55397 changes that are accepted in the 2.2.x branch > STATUS > file are the fixes for these issues. > > I know that 2.4.7 is held up by waiting on APR 1.5 but the vast majority of > Subversion users are still using 2.2.x. So in the meantime it'd be really > nice > if we could get the 2.2.x release done. I'd be happy to take on some of > the > work myself if someone can point me in the right directions. >
