Re: svn commit: r10835 - trunk/subversion/include

On Wed, 2004-09-08 at 10:42, kfogel@collab.net wrote:
> > - * @deprecated Provided for backward compatibility with the 1.1.0 API.
> > + * @deprecated Provided for backward compatibility with the 1.0.0 API.

> Is this the right change?

Of course it's the right change. We're deprecating the function in 1.1;
it's provided for backward compatibility with 1.0.

A separate question is whether the code was right before, when we
thought we were deprecating the function in 1.2:

> When deprecating something, we should say
> it's "provided for backward compatibility with" the earliest
> Subversion possible, since that implies all later ones anyway.

To me, it makes more sense to state the latest version in which the
function wasn't deprecated. Sure, that doesn't provide as much
information about when the function was first available, but it provides
more information about when the function was last recommended.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 8 20:44:02 2004