Re: Request: Specifications / Requirements that only svn can meet

On May 8, 2009, at 1:15 PM, webpost_at_tigris.org wrote:

> Folks,
>
> I work for a government contractor that is likely to force us into
> using an extremely
> overpriced and unnecessarily complicated version control system
> adored by pointy-haired managers everywhere (you probably know the
> one... :).
>
> I have been asked to submit requirements for our new version control
> system. In an effort to delay or prevent the onset of ill-
> rationality I want to present requirements that can be met *ONLY* by
> svn.
>
> 1. Is there a prepared list of specifications / requirements that
> only svn can meet available somewhere?
>
> 2. If not or there are additional requirements you folks know about
> please mention them on the list.
>
> My deadline for submitting this list is COB Monday, 11 May 2009.
> I'll be happy to wrap up the discussions here with a summery of svn
> only requirements so that others can benefit.

How about:

- Has support for write-through proxies that allow you to have remote
repositories at remote offices that have a local cache for very fast
read operations. This also supports disaster recovery in that a copy
of the repository is at a very remote location.

- Supports hot backups of the repository; no down time is required.

- Supports mirroring/backup repositories that will have a copy of any
commits in the master repository within one second of a commit in the
master repository (using svnsync).

- Support on all major platforms:
   Windows
   Linux
   Mac OS X

- Integrates into all major ticket tracking systems, i.e.
   Jira
   Trac

- Integrates into all major IDEs
   Eclipse
   NetBeans
   Microsoft Visual Studio
   Windows (with Tortoise)

- Very large ecosystem around it.

- No vendor lock-in. No risk that the product will go away and you'll
loose your investment in using it.

- Provides bindings so additional tools can be scripted to it in
popular languages
   Java
   Python
   Perl
   Ruby

- Provides a multi-layer abstraction where code can be written to any
of the layers in Subversion, from direct repository access using
svn.fs and svn.repos up to client access using svn.client.

- Supports constant time branching and tagging operations

- Supports disconnected operations where the client doesn't have to
talk to the server to do all operations.

- Requires a very light server infrastructure is required. Only a
single server is ever required to run a repository for a single company.

- Supports both the lock-modify-unlock and copy-modify-merge models.

- Supports pulling code in from remote repositories so a single piece
of code can be shared into multiple projects with the use of
svn:externals. For example, if you needed some source code from
Apache Ant, you could add an svn:external from your repository at http://example.com/svn/repos
  to http://svn.apache.org/repos/asf/.

- Supports all the different authentication models that Apache and
svnserve support, so it's very flexible. Can use flat text files,
LDAP, ActiveDirectory, SASL, etc.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<blair_at_orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2149568
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].