Re: Dependency versioning question

2013-06-06 Thread Greg Stein
On Wed, Jun 5, 2013 at 8:01 PM, Ben Reser wrote: > On Thu, Jun 6, 2013 at 12:50 AM, Greg Stein wrote: >> 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? >> >

RE: Dependency versioning question

2013-06-06 Thread Bert Huijben
> -Original Message- > From: Ben Reser [mailto:b...@reser.org] > Sent: donderdag 6 juni 2013 02:01 > To: Greg Stein > Cc: Subversion Development > Subject: Re: Dependency versioning question > > On Thu, Jun 6, 2013 at 12:50 AM, Greg Stein wrote: > > Within

Re: Dependency versioning question

2013-06-05 Thread Ben Reser
On Thu, Jun 6, 2013 at 12:50 AM, Greg Stein wrote: > 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

Re: Dependency versioning question

2013-06-05 Thread Justin Erenkrantz
+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 back

Dependency versioning question

2013-06-05 Thread Greg Stein
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. With