On Tue, Jun 28, 2011 at 11:20 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> hwright_at_apache.org wrote on Tue, Jun 28, 2011 at 02:46:36 -0000:
>> +<p>Subversion extends the APR guidelines to cover client/server
>> +compatibility questions:</p>
>> +
>> +<ol>
>> +
>> +<li><p>A patch or minor number release of a server (or client) never
>> + breaks compatibility with a client (or server) in the same
>> + major line. However, new features offered by the release might
>> + be unsupported without a corresponding upgrade to the other
>> + side of the connection. For updating ra_svn code specifically,
>> + please observe these principles:</p>
>> +
>> + <ol>
>> +
>> + <li><p>Fields can be added to any tuple; old clients will simply
>> + ignore them. (Right now, the marshalling implementation
>> + does not let you put number or boolean values in the
>> + optional part of a tuple, but changing that will not affect
>> + the protocol.)</p>
>> +
>> + <p>We can use this mechanism when information is added to an
>> + API call.</p>
>> + </li>
>
> ra_svn-specific information doesn't seem to belong here.
>
> It could live in libsvn_ra_svn/protocol, or we could put together an
> HTML page with the "Compatibility considerations" for each module
> (since, for example, wc.db and FSFS and ra_dav and shared library ABI
> each have their own set of concerns)... but on the "How to make
> a release" it seems inappropriate.
I agree. This content has lived here for quite some time, but we
could probably find it another home. I don't have an imminent plans
to do so, however.
-Hyrum
Received on 2011-06-28 20:20:50 CEST