Thursday, August 19, 2004

If anyone can help shed any light on this area for me I would be most grateful. I was introduced to the wonderful world of CVS whilst working at Daemon and now they are going to implement a system at my current company. The question is, what is the best route to take for web development. The CVS with winCVS or tortoise client or subVersion? Can Dreamweaver MX 2004 hook up to subVersion via webDAV as the designers and developers are already familiar with the Dreamweaver's site management interface? Are there any GUI's available for subVersion?

Jon 9:26 AM Permalink

Comments:

Came across this the other day:
http://www.collab.net/developers/tools/

Check out the clients for both subversion and cvs.

Have yet to migrate over yet, but I am chomping at the bit to get something set up. Curious to hear what others have to say about their experiences with massive binaries in these repository systems.

~Mathew

posted by Anonymous Anonymous : 11:47 AM

CVS is old and therefore rock solid, if not without its annoying twists. Whether these quirks will really matter is another questions and one that you probably won't find out until you use it.

Subversion is slightly riskier, being newer, but it has a lot of hype around it... Don't know whether that means it is any good though!

posted by Blogger James : 6:37 PM

We use Subversion and on a windows system Tortoisesvn integrates with your file explorer. If a directory is under versioning the folder icon has an added sign (a green tick). With a right mouse click on this folder you access the commit, update and other functionality of tortoisesvn.
I have worked with it on a small scale and it's a nice change from Visual Source Safe. There's a lot of features like the log, diffing on different levels and the none lock way of versioning that feel like I always knew I wanted it. The integrated 'none exsisting' interface of tortoisesve takes getting used to but all in all quite refreshing

posted by Anonymous Anonymous : 6:39 PM

I've been looking at the two systems for quite a while now for our studio, and I'm leaning heavily towards Subversion for several reasons:

1. for designers not used to VC, the subversion method of versioning a whole file system seems to make a lot more sense (ie they log in and get the whole project rather than a few files)
2. subversion integrates nicely with apache, using it's authentication, meaning you can integrate it with other systems you may already be running on your intra/extranet (take a look at the trac project @ http://projects.edgewall.com/trac/ for a nice simple project management tool that does this)
3. using tortoisesvn makes using versioned files as simple as normal files, and subversion deals with moving, renaming etc files transparently.
4. you can use webdav to map a subversion repository as a network drive under windows easily, so I assume it will work with DW

If you've not done so already I'd recommend you look at:
http://svnbook.red-bean.com/ : complete online 'using subversion' book
http://tortoisesvn.tigris.org/docs/TortoiseSVN_en/ch03.html : invaluable if you're setting up a server on windows

Cheers,
Adam
http://www.randommedia.co.uk

posted by Anonymous Anonymous : 9:21 PM

Post a Comment