1) Revision control or No? if yes, which? Alienbrain and Perforce, but soon Perforce only
2) Do developers work on live files (ie. files seen by general users) or in individual sandboxes? Trying to encourage working on live files as much as possible. 3) Do you use Unit tests? We enforce units and many other settings. 4) Are updates done in batch as an application release, or as needed per file? What is the update procedure? We do not update applications (MAYA) during projects. 5) How many developers? about 90 full time, maybe 5 contract Yury On Tue, Mar 10, 2009 at 1:08 PM, Ian Jones <[email protected]> wrote: > > 1) Revision control or No? if yes, which? > Yes - svn > > 2) Do developers work on live files (ie. files seen by general users) > or in individual sandboxes? > All developers work on a local checkout and commit to trunk when satisfied. > All users run off a network mirror of /trunk > > Branches are used for larger changes to allow for intermediate commits > (not mirrored to users) and peer-review. Juniors/Part-time technical > artists work in branches to inspire peer-review/teaching by leads (who > integrate changes to trunk and are responsible for stability). > > 3) Do you use Unit tests? > On some systems but not all. > > 4) Are updates done in batch as an application release, or as needed > per file? What is the update procedure? > As needed per file for local users, stable tag released as packages > for off-site/outsource teams. > > 5) How many developers? > 3 dedicated, 6 part-time > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/python_inside_maya -~----------~----~----~----~------~----~------~--~---
