API-changing releases was Re: concerns about issue #1682

--On Thursday, January 8, 2004 2:33 PM -0600 kfogel@collab.net wrote:

> If you believe (as I do) that we are *bound* to discover more API
> issues after we release 1.0 anyway, and that they will necessitate an
> API-changing release sooner rather than later anyway, then this patch
> should be left out of 1.0.

Once we hit 1.0, you can't change any existing API prototypes until 2.0.

So, say, if we change our parameters to svn_client_blame, we have to have
the old version as svn_client_blame and the new entry point as
svn_client_blame2 (or something like that to make the names different).

Just want to make sure we're all on the same page here... -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 8 23:34:57 2004