It does beg that question.  The reason is to suit our workflow.  Our
studio is broken down into feature teams (cross discipline teams). Along
with that data is corresponding source code and also builds that are
checked in by continuous integration.

 

The workflow is:

 

-          Programmer makes change, which is either enabling some new
content change, or even requires content fixes.

-          Build gets spat out and checked in 10 minutes later

-          User syncs to that branches build, makes content change in
that branch

 

Put another way, imagine a scenario where you have one team responsible
for adding vehicles to your game, and another team for adding weapons.
Those two teams are on separate branches in our model.

 

Part of the complexity for us (without getting into the detail) is that
the binary data isn't stuff like bitmaps, its kind of like binary xml
files that references code assemblies

 

 

 

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Butcher, Justin
Sent: Wednesday, October 24, 2007 11:30 AM
To: [email protected]
Subject: RE: [OzTFS] Branched binary assets in TFS [SEC=UNOFFICIAL]

 

I'd have to question your use of branches in this way.  If you want the
file only checked out once across branches, then why are you using
brnaches?  Normally branches allow changes to be made indenpendantly
(for all sorts of reasons) and then (optionally) merged back together,
but it sounds like you want these binaries to be only changed in one
branch at a time(?)

 

Cheers,

Justin

 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Karl Burdack (2K Australia)
Sent: Wednesday, 24 October 2007 10:44
To: [email protected]
Subject: [OzTFS] Branched binary assets in TFS

 

 

Hi All, im new to this list; Ive got a burning question I want to throw
out there:  Anyone have an idea how to manage binary assets across
branches.  When working in a simple main trunk, users just use locking
to control this.  However if you have one team on a branch, there
doesn't appear to be a way to "lock across all branches"

 

We have looked at implementing a check out policy, however it doesn't
seem available, only check in policies are possible. 

 

Any ideas?

 

Regards,

Karl Burdack

Technical Director

2K Australia

 

**************************************************************** 

IMPORTANT 

The information transmitted is for the use of the intended recipient
only and may contain confidential and/or legally privileged material.
Any review, re-transmission, disclosure dissemination or other use of,
or taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited and may result
in severe penalties. If you have received this e-mail in error please
notify the Privacy Hotline of the Australian Taxation Office, telephone
13 28 69 and delete all copies of this transmission together with any
attachments. 

**************************************************************** 

OzTFS.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject. View the web archives at
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net OzTFS.com - to
unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject. View the web archives at
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net 




OzTFS.com - to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject. View the web archives at 
http://www.mail-archive.com/[email protected]/

Powered by mailenable.com, supported by www.readify.net

Reply via email to