Just a heads up: the serf devs plan to bump serf from 0.7.x to 1.0.x
on the next release (imminent). That release will contain the error
string functionality discussed a month or so ago (for some work in
ra_serf), and other API changes that shouldn't impact Subversion
While I'm not comfortable with aspects of the serf API, and have
hesitated calling it 1.0, making the next release 0.8.x and keeping
that alive for Subversion's lifetime just doesn't make sense. Thus, we
will bump it to a true 1.0.x release and maintain that for the
lifetime of its primary consumer (svn 1.7.x).
The API changes and new portability substrate will be delivered as
serf 2.0.x, targeting the svn 1.8.x release. The primary goals of
those changes will be to simplify the memory management, connection
and request handling, and the underlying network code in order to
deliver a client library that can be used by most mortals (outside of
the expertise we apply here in svn).
For the Subversion project, we'll want to bump the various "minimum
required version" scattered around the code to 1.0.x. We may be able
to do a serf release with the new version number ASAP, so that svn can
start updating the version requirements.
Please let me/serf know if you have any thoughts/concerns.
Received on 2011-06-22 06:12:37 CEST