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

Re: Speeding up workspace

From: Ruslan Sivak <russ_at_vshift.com>
Date: Tue, 17 Feb 2009 10:36:03 -0500

Bob Archer wrote:
>> Additionally, you seem to have a lot of experience in the development,
>> test and release of a bigger software package. Otherwise I can't imagine
>> why you suggest implementing a really major code change simply weeks
>> before release after a several month development period.
> I didn't hear anyone say it had to be done in 1.6.0... can a new feature not be added to 1.6.1? Or are no features added in that level of release? Actually, this could possible be considered a fix since it doesn't add new features?
> What is the time frame for 1.7? Last I heard 1.6 was due out in December. No, I'm not complaining, I just know that stuff takes longer than expected sometimes.
> I very much appreciate the time given by the volunteers and those that may be paid to work on it. I understand being pragmatic about what goes into a release.
> BOb
I think someone posted earlier that 1.6 has already been branched, and
this would require a working copy update. I wonder if this can be done
as an option or something? Maybe when you install Tortoise or configure
Subclipse there could be an option for workspace type, and it could be
marked experimental? I distinctly remember Tortoise having an option to
rename the .svn folders to preserve compatibility with Visual Studio -
perhaps this could be something similar?

Also, while vendors use the working copy api to some extent - they also
get to do things their own way, I believe. Could the developers of
Tortoise and perhaps SVNKit/JavaHL decide to implement such a patch, and
do it without needing to have anything done in the core SVN for it?



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-17 16:37:22 CET

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

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