• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Thoughts on choosing a source code control system?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Thoughts on choosing a source code control system?


  • Subject: Re: Thoughts on choosing a source code control system?
  • From: Mark Morris <email@hidden>
  • Date: Sun, 12 Mar 2006 21:13:06 -0600

My experience goes along with Janine's. Even when it's just me on a project, I still prefer to use source control. For me, the ability to get back to any previous version of a file or to a previous release is worth the small overhead, and I'm not sure how I would manage collaboration without it.

I've been using cvs for many years, and was very happy with the CVL client (from <www.sente.ch>). However, I've recently started using Subversion, due to the improvements over cvs, and simply to become familiar with it. I'm just using the command line and Xcode's integration, and that seems acceptable until it gets improved or until I find a better client.

Regards,
Mark

On Mar 12, 2006, at 7:49 PM, email@hidden wrote:

The first couple of years we were in business I mostly worked by myself (we had other programmers but they each had their own project). My source code control method was to make a copy of the source file, with the date appended to the name, before I worked on it. Other than the occasional time when I forgot to do this, the method worked fine and served me well. Having all the previous versions of the file right there came in very handy on more than one occasion.

However, time marched on and I started working on one website with several other programmers; we were all doing maintenance work and so there was no way to prevent people from stepping on each other. That was when we adopted CVS, because it was the only package we all knew how to use. Least pain for most gain.

In the beginning our WO projects will be mine alone, so I could forgo source code control once again, but using it is now part of my work process and I don't really want to go back to having to remember to make copies of files. Having it also makes it easier to transfer only stable code to the live site.

So while I don't dispute your assertion, I think having one is the right choice for us. Thankfully I am the management (or damagement, take your pick :) and I get to make the hopefully informed decisions that others will follow.

janine
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Thoughts on choosing a source code control system? (From: email@hidden)
 >Re: Thoughts on choosing a source code control system? (From: Ian Joyner <email@hidden>)
 >Re: Thoughts on choosing a source code control system? (From: email@hidden)

  • Prev by Date: Re: Thoughts on choosing a source code control system?
  • Next by Date: Re: Thoughts on choosing a source code control system?
  • Previous by thread: Re: Thoughts on choosing a source code control system?
  • Next by thread: Re: Thoughts on choosing a source code control system?
  • Index(es):
    • Date
    • Thread