• 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: Need CVS Advice
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Need CVS Advice


  • Subject: Re: Need CVS Advice
  • From: Bill Bumgarner <email@hidden>
  • Date: Thu, 4 Aug 2005 14:28:39 -0700

On Aug 4, 2005, at 1:15 PM, Randy Bradley wrote:
On Aug 2, 2005, at 8:46 PM, Gary Yuen wrote:
you could try Perforce. I've been using it for a little while and really love it. The P4V client is amazing. I haven't tried branching yet though people say it's much nicer than Subversion. Free for 2 users and I believe Apple uses it.
Thanks Gary. I was under the impression that it was $800 so I didn't pursue it further. I will sure take a look at it though at that price!

Creating the CVS branches and removing/adding files (mostly icons) was easy enough. However, my limited documentation gives examples of merging branches onto the main trunk. Of course, I'm wanting to do the opposite, merge patches from the main trunk onto the branches. I will look for a cvs discussion list to continue this topic.

Apple uses a mix of CVS, Perforce, and Subversion. Many teams are moving away from CVS in favor of Subversion. Perforce is used by a number of groups, but they tend to be isolated projects.


Development Technologies has a growing number of projects living in Subversion repositories. It is kind of funny -- as you move away from CVS, you begin to realize how much CVS really limited your development process. I have discovered all kinds of useful procedures that I assumed were useless, but which turned out to be just prohibitively hard to support with CVS. For example, Subversion's no cost branching means that many engineers will cut a branch to go explore some random, potentially risky, idea. That is, Subversion gives one more freedom to innovate with less risk to the overall project.

Subversion and Perforce offer a similar set of features. Personally, I prefer Subversion for a number of reasons; http access to repositories, mounting a repository in the Finder to drag out a copy of HEAD, awesome development team that is really responsive, and that it is open source, thus I know I can go in and hack it to recover data if I absolutely positively have to (which has not happened yet, unlike CVS). I also had a really bad experience with Perforce that involved multiple days of downtime for a good sized team of expensive contractors.

Many people swear by Perforce, though, and it is obviously a great product.

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


References: 
 >Need CVS Advice (From: Randy Bradley <email@hidden>)
 >Re: Need CVS Advice (From: Gary Yuen <email@hidden>)
 >Re: Need CVS Advice (From: Randy Bradley <email@hidden>)

  • Prev by Date: Creating a dmg (was Re: NSWorkspace)
  • Next by Date: Which control is the field editor standing in for?
  • Previous by thread: Re: Need CVS Advice
  • Next by thread: NSStatusBar generates Sigtrap
  • Index(es):
    • Date
    • Thread