Eric Lee wrote:
> What feature(s) will svn 1.7 provides ?
> Will it support some functions that already on some others v.c. software.
> I have seen some discuss before but no more now.

1.7 is primarily a vehicle for the delivery of our revamped working copy
code. Sounds boring, I know. But it should bring immediate performance
enhancements, as well as set the stage for a number of additional features
and improvements that we've been talking about for a long time but haven't
had decent support in the working copy implementation to seriously consider.
Now, we're seriously considering them. :-)

1.7 also bring improvements to the HTTP protocol (again, for performance), a
new 'svn patch' functionality, and a number of other small features and
bugfixes.

> Also, shall the svn 1.7 be a first version that provides beta testing
> before it was final release on each version.
> I do feel that just like a unit testing that test a piece of code
> before announce it publicly.
>
> Just a thought and please correct me if I'am wrong !!

Our big releases (ones that end in ".0") do generally see a series of beta
and/or release-candidate releases before being called final. They always
have, and that won't change.

Formally speaking, our patch releases (the "X" in 1.6.X) are tested via unit
tests only (by at least 3 folks on Windows, and 3 on Unix flavors). Of
course, many of the devs run the HEAD of either trunk or the latest release
stream for their day-to-day work, too. We don't typically put out beta or
RC releases for these patches, though, and I'm not sure the overhead of such
is typically justified. That said, you are more than welcome to run the
HEAD of the branches/1.6.x branch daily like I (and others) do, and
effectively test that code before it ever sees a release.