Something to think about ...do we want to migrate to Subversion ....


Begin forwarded message:


From: Ted Husted <[EMAIL PROTECTED]>
Date: Sat Mar 27, 2004  5:31:17  PM US/Pacific
To: <[EMAIL PROTECTED]>
Subject: Fwd: [subversion] Subversion for eXtreme Refactoring
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>

So, I'm sure many of us saw this on the Jakarta Commons DEV list, but I thought it might be worth bringing up in the context of our refactoring discussions.

I have no strong feelings myself. Though, I'm sure we all realize that eventually we'll be using Subversion.

To date, I've never done more with CVS than what I needed to get through the day. But I think that might change once I end up working on a project that uses Subversion. :)

For anyone wondering what is all about, see <http://subversion.tigris.org/> and <http://svnbook.red-bean.com/>.

-Ted.

--- Original Message ---
From: "Alex Karasulu" <[EMAIL PROTECTED]>
To: 'Jakarta Commons Developers List' <[EMAIL PROTECTED]>
Sent: Sat, 27 Mar 2004 14:54:36 -0500
Subject: [subversion] Subversion for eXtreme Refactoring ( was [HiveMind] Discuss: CVS or Subversion?)


Subversion for eXtreme Refactoring
==================================

Subversion affords us a more liberty.  Besides the obvious renaming
and deleting of files and directories without the loss of history
etcetera, we find that our development style can be geared towards
XP.  These features are changing our outlook.  We are no longer
worried about chewing up a repository to re-factor on a whim.  I
personally have re-factored conservatively on CVS because there was
no way to easy way to cleanup the consequences afterwards: loss of
history and empty directories.  But now there are no inhibitions
with subversion so we're free to be liberal with re-factoring -
it's the way we code.  Bang something rough out and then gradually
reshape it as we discover new things along the way.  Plus the ease
of branching by just copying directories and merging them makes
large re-factoring efforts without disrupting development a breeze.
 These features have for these reasons improved our development
style and the quality of our code.  Subversion goes hand in hand
with XP!  It's the preferred VCS for extreme programmers!

Going back to CVS is not an option for me after tasting development
using subversion: it would mean going backwards.  The best
description I can give of the having to use CVS after using
subversion is when I have to use dial up rather than high speed
internet access.  It's just frustrating.

Subversion is the future that fits the latest paradigms in software
development.  I cannot stress the importance of the positive
effects it will have for development here at the ASF not to mention
for infrastructure.  And ultimately the transition will have to
happen at some point.

BTW in the past I have been a CVS consult and lived and swore by it
since it put food on the table.  I cannot overstate how emphatic I
have been regarding CVS.  It was a religion for me.  Now after
years of using CVS, I swear by subversion and that's got to be
worth something when said by a CVS diehard.

Regards,
Alex


-------------------------------------------------------------------- - To unsubscribe, e-mail: commons-dev- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to