[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Beyond Source Code Control

From: Jared Hardy <jaredhardy_at_gmail.com>
Date: 2007-11-19 11:18:50 CET

My company currently uses Subversion for most of our binary files. We
are video game developers, so this includes documents of all kinds,
spreadsheets, illustrations, 3D models, animations, screen shots,
textures, executables, DLLs, batch scripts, etc. We use exclusive
locks on most assets, to prevent editors from stomping on each other,
because most art file types used here don't have working merge tools
(yet). I'm hoping to transition to open-standard file types like SVG
and COLLADA in the future, which may open up the possibility of visual
merge tools. Some limited merge tools for BMP, and similar image
formats, already exist. If we could define a default merge type, it
would be "whomever has the lock first wins".
    This is still "source control", in the sense that we consider our
art files to be source data, that get "compiled" into custom
real-time-data formats. The main 2 reasons we use Subversion
repositories for this data are: 1. exclusive-lock tracking prevents
loss from overlapping work, and 2. binary delta history saves storage
space on the server, as well as network bandwidth on updates. The
flexible authentication options, and WebDAV over SSL capability, are
nice bonuses, but aren't deal-breakers. The WC format is slow on our
WinXP NTFS clients, so we're working on using SVK as the main client
interface, with custom extensions for maintaining lock properties on
the central server repository.

:) Jred

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 19 11:19:11 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.