Comments on: Managing Creative Assets – 2: Distributed Version Control Systems http://www.arunrocks.com/blog/archives/2009/12/13/managing-creative-assets-2/ Representing Anti-monotonistic Tendencies Thu, 29 Jul 2010 02:07:12 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: Managing Creative Assets – 1 | Arunrockshttp://www.arunrocks.com/blog/archives/2009/12/13/managing-creative-assets-2/comment-page-1/#comment-4860 Managing Creative Assets – 1 | Arunrocks Tue, 06 Jul 2010 08:33:22 +0000 http://www.arunrocks.com/blog/?p=171#comment-4860 <p>[...] of drifting in the opposite direction too, as in the case of the Second System effect.In the next part, we will be introduced to two kinds of version control systems – Centralized and Distributed; [...]</p> [...] of drifting in the opposite direction too, as in the case of the Second System effect.In the next part, we will be introduced to two kinds of version control systems – Centralized and Distributed; [...]

]]> By: Arun Bhaihttp://www.arunrocks.com/blog/archives/2009/12/13/managing-creative-assets-2/comment-page-1/#comment-808 Arun Bhai Tue, 15 Dec 2009 03:17:31 +0000 http://www.arunrocks.com/blog/?p=171#comment-808 <p>Glad to know that TortoiseHg has truly lowered the barrier of entry to version control system to an average user. In fact, I would be concluding this series with a visual tutorial of TortoiseHg.</p> Glad to know that TortoiseHg has truly lowered the barrier of entry to version control system to an average user. In fact, I would be concluding this series with a visual tutorial of TortoiseHg.

]]> By: Arun Bhaihttp://www.arunrocks.com/blog/archives/2009/12/13/managing-creative-assets-2/comment-page-1/#comment-806 Arun Bhai Tue, 15 Dec 2009 03:11:24 +0000 http://www.arunrocks.com/blog/?p=171#comment-806 <p>Thank you Krish for your comment. I must admit that unless I describe my DVCS workflow (which I have planned for the next part), some of these points might sound subjective or inaccurate. For e.g. most DVCS do not delete the file after checkin enabling you to continue work normally, as before.</p><p>Your last point is quite valid. Version control is not a substitute for a good backup strategy. I recommend backing up the entire repository in an separate storage device or location.</p> Thank you Krish for your comment. I must admit that unless I describe my DVCS workflow (which I have planned for the next part), some of these points might sound subjective or inaccurate. For e.g. most DVCS do not delete the file after checkin enabling you to continue work normally, as before.

Your last point is quite valid. Version control is not a substitute for a good backup strategy. I recommend backing up the entire repository in an separate storage device or location.

]]> By: Roger Gammanshttp://www.arunrocks.com/blog/archives/2009/12/13/managing-creative-assets-2/comment-page-1/#comment-800 Roger Gammans Mon, 14 Dec 2009 22:55:34 +0000 http://www.arunrocks.com/blog/?p=171#comment-800 <p>I've used mercurial very successful for some creative writing and have introduced a number of non-geeks (on windows) to mercurial without to much complaining thanks to the ease of use that tortoiseHg provides.</p><p>In fact I'm in the middle of writing a specialist application for one of the type of writing I do, and it uses mercurial internally as it primary SCM, to allow for various collaborative workflows.</p> I’ve used mercurial very successful for some creative writing and have introduced a number of non-geeks (on windows) to mercurial without to much complaining thanks to the ease of use that tortoiseHg provides.

In fact I’m in the middle of writing a specialist application for one of the type of writing I do, and it uses mercurial internally as it primary SCM, to allow for various collaborative workflows.

]]> By: Krishhttp://www.arunrocks.com/blog/archives/2009/12/13/managing-creative-assets-2/comment-page-1/#comment-799 Krish Mon, 14 Dec 2009 22:23:37 +0000 http://www.arunrocks.com/blog/?p=171#comment-799 <p>A few things are not accurate for VSS (which I don't like either):</p><ul> <li>Remembering to checkout immediately after you import or check-in</li> <li>Weird layout</li> <li>Server must be always running: VSS is just a file system using a client.</li> </ul><p>And the first point is a little suspect too. You can change your sub-working folders in VSS.</p><p>If you are working alone, you should be worrying about backups, if everything is lying on your local hard disk.</p> A few things are not accurate for VSS (which I don’t like either):

  • Remembering to checkout immediately after you import or check-in
  • Weird layout
  • Server must be always running: VSS is just a file system using a client.

And the first point is a little suspect too. You can change your sub-working folders in VSS.

If you are working alone, you should be worrying about backups, if everything is lying on your local hard disk.

]]>