+1 for "no big deal" too, I think.
Depending upon how far we take serf 2.0 and its APIs, a new libsvn_ra_serf2
library may be in order. So, it'd be no different than all of the
libsvn_fs* and libsvn_wc internal changes.
If we altered the RA APIs, then that would be a no-no if we did it in a
backwards-incompatible manner. -- justin
On Thu, Jun 6, 2013 at 8:50 AM, Greg Stein <gstein_at_gmail.com> wrote:
> Hey all,
>
> I've got a question where I'm not quite sure what the answer "should"
> be. While I wrote the rules on versioning components, it never talked
> about cross-component and dependency versioning. For Subversion, we
> said "all svn components should be at the same version".
>
> But dependencies.
>
> Within serf, we're thinking about new models for connection and
> protocol handling. And bumping to 2.0 to make that happen. What is the
> effect upon libsvn_ra_serf and svn in general?
>
> My thinking is "no big deal". That upgrading to svn 1.9 (or 1.10 or
> whatever) would require installation of serf 2.0. All svn APIs would
> remain unchanged, per our own versioning guidelines (both source and
> binary APIs).
>
> Thoughts?
>
> Cheers,
> -g
>
Received on 2013-06-06 01:58:55 CEST