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

Re: Expected post-1.0 release cycle?

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-12-24 03:08:26 CET

On Tue, 2003-12-23 at 21:00, Jack Repenning wrote:
> I'm not sure I follow your "if". I think there's a significant
> difference between the APR scheme and the one I described; basically,
> I've upshifted all the constraints one level. APR allows API change
> with deprecation over minor release changes (A.B.*->A.B'.*), where I
> restricted that to major releases (A.*.*->A'.*.*); similarly, APR
> allows true incompatible changes over major releases, where I allow
> that only over two major releases, with deprecation or
> upwards-compatibility support over single major releases.

I'm a little unclear on how this "deprecation" thing has anything to do
with version numbers. It's just a documentation decision where you say
"if you're thinking about whether to use X now, you should use Y
instead, because some day X might go away." I don't see why that would
be harmful in a minor release, but neither do I see how it would be
terribly valuble, since X can't go away until the next major release
anyway, and then nothing is guaranteed (by the APR rules).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 24 03:09:04 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.