You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by hw...@apache.org on 2010/05/27 16:31:06 UTC
svn commit: r948849 - /subversion/trunk/notes/feedback/hwright-user-visits
Author: hwright
Date: Thu May 27 14:31:06 2010
New Revision: 948849
URL: http://svn.apache.org/viewvc?rev=948849&view=rev
Log:
* notes/feedback/hwright-user-visits:
Add some additional comments sent to me by a user.
Modified:
subversion/trunk/notes/feedback/hwright-user-visits
Modified: subversion/trunk/notes/feedback/hwright-user-visits
URL: http://svn.apache.org/viewvc/subversion/trunk/notes/feedback/hwright-user-visits?rev=948849&r1=948848&r2=948849&view=diff
==============================================================================
--- subversion/trunk/notes/feedback/hwright-user-visits (original)
+++ subversion/trunk/notes/feedback/hwright-user-visits Thu May 27 14:31:06 2010
@@ -74,6 +74,51 @@ A lot of the Concerns are actually somew
attempt to vet them, and if found justifiable, implement them.
+User 3
+======
+
+Background
+----------
+Large multinational corporate, many regions each with relatively few developers
+(10-20 per region say), couple of hundred in HQ. Beginning to work with
+outsourced development centres. Moved from VSS to SVN 18 months ago (but
+planning longer).
+
+
+Concerns
+--------
+* Performance. Base product is 20,000 files in a few hundred Mb Data, plus
+ smaller modules. Initial checkin of the base often fails and has to be
+ performed piecemeal. Some log commands take a while, TortoiseSVN's revision
+ graph is unusable.
+* Server-based configuration. It's not nice when a user forgets to set his
+ global-excludes for example.
+* Obliterate support would be nice to clean up the repo.
+* Archiving support also - ie to delete revisions over 2 years old, for
+ example, whilst keeping newer revisions.
+* Better admin tools in general, our repo is 12Gb now, so svnadmin
+ dump/filter/load is almost impractical.
+* Tags are useless (almost), we'd want revnum aliases too. Especially would
+ like to create a single tag, but then use that to hold all releases - eg,
+ 1 tag branch where each revision is a release. Merging makes this slightly
+ difficult and not suitable as we just want to 'merge' onto the tag by copying
+ the current file over, not by merging revisions, not by doing a checkout and
+ commit.
+* Search - there's no good ability that can index a repo for searching, nor to
+ search log comments.
+
+Places Subversions stands out
+-----------------------------
+* Simple and easy to use.
+* Good repository view - the directory structure is easy to understand and has
+ good visibility.
+* Excellent integration with other tools. "right thing done right" when
+ combined with other best-of-breed tools can be beautiful (eg bugtracker,
+ requirements/project management, document repositories), plus other utilities
+ such as TortoiseSVN and Apache views.
+* Svnsync.
+
+
Other Users
===========
I talked to one user who had actually written a custom client, which allowed
Re: svn commit: r948849 - notes/feedback/hwright-user-visits
Posted by Stefan Sperling <st...@elego.de>.
On Thu, May 27, 2010 at 05:53:42PM +0100, Julian Foad wrote:
> * Long option names
> -- finds the long names irritating and wants short equivalents?
I think we've already addressed this request, at least partly.
I've added a couple of option aliases on trunk a while back.
I did it because I got tired of typing --reintegrate and other such long options.
Maybe the user had the same problem as I did.
We could review more options in need of short aliases.
The current list of aliases can be seen in subversion/svn/main.c.
And I agree with your request for more detailed information about the
desired enhancements.
Stefan
Re: svn commit: r948849 - notes/feedback/hwright-user-visits
Posted by Julian Foad <ju...@wandisco.com>.
hwright@apache.org wrote:
> * notes/feedback/hwright-user-visits:
> Add some additional comments sent to me by a user.
That's good.
Any chance of more details on the concerns of User 2? Particularly:
* No zero-change commit support.
-- supporting empty commits? what for?
* Long option names
-- finds the long names irritating and wants short equivalents?
* Merge ancestry issues are painful
-- anything specific, or an example of what this means?
* Want 'svn diff@WORKING'
-- what?
* Long-running merge operations
-- it's just a pain that they take so long, or something else?
- Julian
Re: svn commit: r948849 - notes/feedback/hwright-user-visits
Posted by Julian Foad <ju...@wandisco.com>.
hwright@apache.org wrote:
> * notes/feedback/hwright-user-visits:
> Add some additional comments sent to me by a user.
That's good.
Any chance of more details on the concerns of User 2? Particularly:
* No zero-change commit support.
-- supporting empty commits? what for?
* Long option names
-- finds the long names irritating and wants short equivalents?
* Merge ancestry issues are painful
-- anything specific, or an example of what this means?
* Want 'svn diff@WORKING'
-- what?
* Long-running merge operations
-- it's just a pain that they take so long, or something else?
- Julian