[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-01-09 17:57:18 CET

On Fri, 2004-01-09 at 00:44, kfogel@collab.net wrote:
> So why are we trapping ourselves into this?

If we expect our API to be successful, then we should expect that when
we make an incompatible API change, it will take a while--possibly
months or years--before all interesting third-party programs are updated
to use the new API. gnucash still hasn't finished porting to GNOME 2.

Therefore, when we make an API-breaking release, we need to paint a
bright red flag on it which tells people not to upgrade by replacing the
old version of svn, but instead to co-locate the new version with the
old version.

With your scheme, there is no such bright red flag; not only would the
initial version number not change, but a middle version number change
*might or might not* signal an incompatible API change.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 9 17:58:13 2004

This is an archived mail posted to the Subversion Dev mailing list.