You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <hu...@apache.org> on 2004/03/28 03:31:17 UTC

Fwd: [subversion] Subversion for eXtreme Refactoring

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" <ao...@bellsouth.net>
To: 'Jakarta Commons Developers List' <co...@jakarta.apache.org> 
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-
> unsubscribe@jakarta.apache.org For additional commands, e-mail:
> commons-dev-help@jakarta.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org