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

Re: future of our "experimental" features

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 24 Jan 2020 15:48:29 +0100

On Fri, Jan 24, 2020 at 01:39:58PM +0000, Paul Hammant wrote:
> I think y'all should promote something to mainstream, even if the
> performance isn't what you want it to be (for this feature). Better slow
> IMO, than "does the wrong thing". If y'all promote neither it'll just
> decay away from trunk and then risk never going live. As it doesn't affect
> any existing part of Subversion its case for merging into trunk is stronger.

If a feature doesn't fit neatly into the design goals of Subversion
then leaving it out is a better option. Shipping new features in a
half-baked state implies an increased maintenance burden which we
simply cannot afford.

Creating a working copy in a hidden directory is a great prototype
but not something to put into a release.

> I cobbled together a "VCS Nirvana" blog entry some days ago -

I don't see how posting a wishlist like benefits this discussion.
Our goal is to get SVN 1.14 out the door with severely limited resources.
It is not to write a new VCS or even compare SVN to anything else that's
available and try to "catch up" somehow. Please stop doing that.
Received on 2020-01-24 15:48:48 CET

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.