Hi Amos,
There is no built-in development framework in SVN like there is in ClearCase UCM. With SVN you can role your own development framework using the hooks, but that's very different from having one ready-made for you. IMHO the decision point is the size of the organization. With less that 30 developers in not more than two locations you can afford to make your own procedures and get by. At Tivoli in Austin (shortly before the sale to IBM), when we got to 50 developers the cracks started to show.

 - yba


On Thu, 11 Oct 2007, Amos Shapira wrote:

Date: Thu, 11 Oct 2007 04:24:12 +0000
From: Amos Shapira <[EMAIL PROTECTED]>
To: linux-il@cs.huji.ac.il
Subject: Re: [OT] SVN commercial support

On 11/10/2007, Jonathan Ben Avraham <[EMAIL PROTECTED]> wrote:

developers working in one location. Once you go above that number there
begin to be project management issues such as the need to lock down
branches, define releases and other build types, and impose development
discipline. This is where SVN and CVS fail miserably and ClearCase


"impose development discipline" is something I'm always in favour off,
especially after working for a company which did it pretty much perfectly,
but I'm not sure why you take this as a point against SVN.
What about Repository Hooks (
http://svnbook.red-bean.com/en/1.4/svn-book.html#svn.reposadmin.create.hooks
)?

Not that I speak from personal experience, so I'm open to learn new points
about any tools.

Cheers,

--Amos
(Who's now in the middle of an ongoing crusade to teach my organization
proper use of SVN/Bugzilla and other tools).


--
 EE 77 7F 30 4A 64 2E C5  83 5F E7 49 A6 82 29 BA    ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
     - [EMAIL PROTECTED] - tel: +972.2.679.5364, http://www.tkos.co.il -

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to