Seems to me the main benefit of including non-text files in a
Subversion tree would be product configuration control. Placing all the
text files, graphic files, and proprietary-format files which belong to a
particular product-level revision into the same branch of a CVS or
Subversion tree would keep them together and prevent mixups. This is one of
the classic problems of engineering revision control. Most Drafting
departments solve it with manual procedures, if they solve it at all.
A set of mutually consistent design files may be kept in the same
branch. Once a set of files is approved for production and products are
shipped, that branch should be placed under ECO control, given a top-level
revision letter, and frozen permanently. Development would then be
continued on a new branch, with unchanged files referenced in the new
branch.
If someone can figure out the appropriate logic and write rules for
use of the tree, OGP will have made its contribution to the advancement of
the engineering services profession.
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
