Skip to main content
Graphic Design

Return to Answer

typo fix
Source Link
plainclothes
plainclothes
  • 17.6k
  • 41
  • 75

Version Cue, in my experience, is garbage. I have two systems for two different teams going right now.

SVN via Cornerstone
I've been running a large volume of creative work through SVN via Cornerstone for Mac for over a year now. It's a very slick and easy to use app that makes VC seem easy. It doesn't provide visual previews of the files like I believe PixelNovel does but our detailed change notes have been more than adequate. Cornerstone has been a very robust solution for the localized team I work in.

Git via SourceTree
I also just begunbegan coordinating a remote team via Bitbucket.org using SourceTree. Git has a little steeper learning curve at first but it's working well for us. We're essentially following the same principles as the SVN set-up, ie detailed change logs.

The differences
Git operates under the model that each user downloads the whole repository (history and all) to their machine. To keep this manageable, it's best to have a separate repository for each project. It's nice to have a repository that's easy to archive and retire when the project is over.

SVN, on the other hand, allows the user to checkout the latest version of a directory within a repository. If you want to roll back to a previous version you must connect to the server. This is a good system for a centralized repository that contains all the projects under way. I prefer it for a high volume environment where many simultaneous and often interconnected projects are underway.

Version Cue, in my experience, is garbage. I have two systems for two different teams going right now.

SVN via Cornerstone
I've been running a large volume of creative work through SVN via Cornerstone for Mac for over a year now. It's a very slick and easy to use app that makes VC seem easy. It doesn't provide visual previews of the files like I believe PixelNovel does but our detailed change notes have been more than adequate. Cornerstone has been a very robust solution for the localized team I work in.

Git via SourceTree
I also just begun coordinating a remote team via Bitbucket.org using SourceTree. Git has a little steeper learning curve at first but it's working well for us. We're essentially following the same principles as the SVN set-up, ie detailed change logs.

The differences
Git operates under the model that each user downloads the whole repository (history and all) to their machine. To keep this manageable, it's best to have a separate repository for each project. It's nice to have a repository that's easy to archive and retire when the project is over.

SVN, on the other hand, allows the user to checkout the latest version of a directory within a repository. If you want to roll back to a previous version you must connect to the server. This is a good system for a centralized repository that contains all the projects under way. I prefer it for a high volume environment where many simultaneous and often interconnected projects are underway.

Version Cue, in my experience, is garbage. I have two systems for two different teams going right now.

SVN via Cornerstone
I've been running a large volume of creative work through SVN via Cornerstone for Mac for over a year now. It's a very slick and easy to use app that makes VC seem easy. It doesn't provide visual previews of the files like I believe PixelNovel does but our detailed change notes have been more than adequate. Cornerstone has been a very robust solution for the localized team I work in.

Git via SourceTree
I also just began coordinating a remote team via Bitbucket.org using SourceTree. Git has a little steeper learning curve at first but it's working well for us. We're essentially following the same principles as the SVN set-up, ie detailed change logs.

The differences
Git operates under the model that each user downloads the whole repository (history and all) to their machine. To keep this manageable, it's best to have a separate repository for each project. It's nice to have a repository that's easy to archive and retire when the project is over.

SVN, on the other hand, allows the user to checkout the latest version of a directory within a repository. If you want to roll back to a previous version you must connect to the server. This is a good system for a centralized repository that contains all the projects under way. I prefer it for a high volume environment where many simultaneous and often interconnected projects are underway.

Source Link
plainclothes
plainclothes
  • 17.6k
  • 41
  • 75

Version Cue, in my experience, is garbage. I have two systems for two different teams going right now.

SVN via Cornerstone
I've been running a large volume of creative work through SVN via Cornerstone for Mac for over a year now. It's a very slick and easy to use app that makes VC seem easy. It doesn't provide visual previews of the files like I believe PixelNovel does but our detailed change notes have been more than adequate. Cornerstone has been a very robust solution for the localized team I work in.

Git via SourceTree
I also just begun coordinating a remote team via Bitbucket.org using SourceTree. Git has a little steeper learning curve at first but it's working well for us. We're essentially following the same principles as the SVN set-up, ie detailed change logs.

The differences
Git operates under the model that each user downloads the whole repository (history and all) to their machine. To keep this manageable, it's best to have a separate repository for each project. It's nice to have a repository that's easy to archive and retire when the project is over.

SVN, on the other hand, allows the user to checkout the latest version of a directory within a repository. If you want to roll back to a previous version you must connect to the server. This is a good system for a centralized repository that contains all the projects under way. I prefer it for a high volume environment where many simultaneous and often interconnected projects are underway.