On 11. 12. 2025 19:59, Daniel Sahlberg wrote:
Hi,
Prompted by Evgeny's suggestion to move forward with releasing Subversion
1.15.0[1], I'd like to suggest getting a new minor release of Serf out of
the door as well - preferrably first!
There are a few features in Subversion that depend on recent development in
Serf (for example the error reporting) and it would be nice to have it
released together.
Brane has made a summary in Jira, see SERF-208[2], open points copied below:
* Generalized error callbacks, discussed in [3]. From what I can see we
have an error callback mechanism that works for SSL errors. There is also
code in Subversion to support this. We need to decide if [a] We are happy
with the current situation, or [b] Can someone step up to improve it.
Personally, I'm leaning towards [a].
* Issue SERF-195, which is a substantial rewrite of the request queues. The
code is in a separate branch SERF-195. The code looks good to me but I
haven't analyzed in detail. It should be possible to merge to trunk.
* Issue SERF-209, concerning intermitent test suite failures under MacOS. I
would suggest to leave this aside for later.
Can we get these decided/merged and roll a release? I think it would be
good to do this in trunk before branching.
Kind regards,
Daniel
[1]https://lists.apache.org/thread/x0s1c8jolql5hdkq40jm3jfnpm6wjp9s
[2]https://issues.apache.org/jira/browse/SERF-208
[3]https://lists.apache.org/thread/7khn697o2srmg8wvqy4t3xyxq4cr8v8v
We dropped the ball again :)
What is left now? I updated the API compatibility table on the web site
some time ago. With, I must say, a lot of fun trying to build all the
Serf releases since 1.0.0, but I somehow succeeded anyway. There's
nothing interesting there.
I'd really like to get this out of the way, if for no other reason than
that we can announce that Subversion 1.15 works with Serf 1.5 (it does,
whether or not we use the experimental feature flag).
My proposal: let's do the final API review and roll the release. Then,
for Subversion 1.16, we can integrate the better error callbacks and
other new features and make them non-experimental, just dependent on the
Serf version.
And then – as discussed with Bert earlier in this thread – we drop the
V1 bucket compatibility and roll Serf-2.0 sooner rather than later.
IIRC there was some discussion of also making one last 1.3.x release?
Because of some known bug?
Just my two groats.
-- Brane
