Hi, I'm very happy to see the rekindled interest in Serf development and the recent work by Brane on the user-defined-authn branch and by Graham on the OpenSSL "certificate by URI" PR. I'm planning on reviewing those things during the weekend. When these are merged (and it doesn't only depend on me, it is of course a team effort reviewing and merging!) we should start thinking about a new release.
I don't think it makes sense to backport to 1.3 - they would add new APIs that require a version bump. The existing 1.4.x branch was created in 2018 and received a few backports the same year but it lacks significant work from trunk, for example Evgeny's OpenSSL3 work in 2022 that led up to the release of 1.3.10. I'm proposing to drop the current 1.4.x branch and create a new one based on trunk. Alternative option to drop 1.4.x completely and instead name the new release 1.5. As far as I understand trunk contains a bunch of HTTP 2-work, but according to Brane earlier on dev@ some is hidden behind #ifdefs that will only expose it if released as Serf 2. Would it make sense to get this released as well? In that case, should we instead aim for Serf 2.0? Alternative option to remove the #ifdefs and declare it stable in Serf 1. Cheers, Daniel
