On 09.02.2010 11:51, Stefan Fuhrmann wrote:
> Hi there,
>
> this is a list of things that could be done in TSVN
> within the 1.7 time frame - still a felt 6 months away.
> Certainly, this is more of a pick list as not all of them
> will be done until the release:
>
> New features:
>
> - merge info display in revgraph
> -> S V Ram is already working on this one
>
> - extend cleanup command to remove various files.
> http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Notes/Feature
> Proposals/Cleanup.txt
> Small improvement. Any volunteers?
We already have the "Delete unversioned items" command
(shift-right-click to see it). This brings up a dialog showing all
unversioned and ignored files/folders to select for deletion.
What would the "Delete other files and folders" do exactly? What 'other'
files/folders?
> - bisect
> http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Notes/Feature
> Proposals/Bisect.txt
> Small improvement. Any volunteers?
Even with your detailed description, I simply can't see any benefit of
implementing this in TSVN at all.
Let's face it: 90% of all users don't even have an automated build
script for their source. Those who have, have a script that doesn't
return TRUE/FALSE for another app to catch.
That might leave ~3% who have such a script to be used. But that's a
build script - most of the time you want to find an offending revision
that breaks a feature, not one that breaks a build. And that reduces the
people who can use this feature even further.
All others will still have to do everything manually - a dialog which
stays open and updates to other testing revisions won't help here much
(if at all).
Does this really justify this much code for something that won't get
used a lot and therefore also won't get tested enough?
> - experimental patch recorder
> (a simple implementation for "offline / pre-recorded commits")
> http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Notes/Feature
> Proposals/PatchRecorder.txt
> Already working on this.
Wouldn't it be better to implement this in the svn library? I'm sure
you'll get commit access if you send your specs to the svn dev list.
> No functional spec available yet for these:
>
> - insert / delete / rename / move / modify externals in repo browser
> (make it work just like any folder)
> I will take this one.
>
> - support nested externals in repo browser (if they legal at all)
> I will take this one.
+1 on these.
> - user-defined property ranges / enum lists etc.
> (i.e. make prop editor easier to use)
>
> - freeze / modify externals upon tag / branch ops
I'll write up some specs for these soon.
> Odd jobs:
>
> - finish LogCache documentation
> - switch to VS2010
VS2010RC is up on MSDN....
> - fully or partly switch to msbuild to speed up build times
Why do you think switching from Nant to msbuild will speed up the build
times?
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2446212
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-09 19:09:47 CET