i'm curious how others structure the releases of their pipelines. Here's a little survey:
1) Revision control or No? if yes, which? 2) Do developers work on live files (ie. files seen by general users) or in individual sandboxes? 3) Do you use Unit tests? 4) Are updates done in batch as an application release, or as needed per file? What is the update procedure? 5) How many developers? I'll be the first to fill it out: 1) Revision control or No? if yes, which? Yes. subversion, hooked up to Eclipse. 2) Do developers work on live files (ie. files seen by general users) or in individual sandboxes? We have one repo. Developers work in their own personal workspaces, and there is one global workspace that everyone else references: global should never be directly edited -- it is only updated via subversion. 3) Do you use Unit tests? Not currently 4) Are updates to the pipe done as an application release, or as needed per file? What is the update procedure? as needed, per file. the developer commits his changes to the repo, then, if desired, updates the live workspace using eclipse or Versions, a standalone subversion tool. he can also put "@autoupdate" in his commit message and a post-commit hook will automatically update the live global copy with the new changes. 5) How many developers? 3 dedicated. 2 part time. -chad --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/python_inside_maya -~----------~----~----~----~------~----~------~--~---
