Put it on tech-artists<http://tech-artists.org/forum/showthread.php?4666-Pipeline-Specifications-for-Versioning>and figured it related equally well to us here.
As part of developing pipeline solutions, I'm working on defining and giving name to the various methods we use in versioning content such as art-work and code. I'm defining them in open-source, wiki-style documents called RFCs stored on GitHub <https://github.com/abstractfactory/rfc> and published at rfc.abstractfactory.io where collaborators fork the corresponding branch and submits pull-requests. The goal of each RFC is to make it possible to reference known solutions in general conversation via short-hand names as opposed to resorting to explanations of what may be thought of as obvious. Thus far I've managed to boil down versioning into exactly two methods, Monolithic and Polylithic; continuous overwriting versus incrementally saving. The overview is given here, rfc.abstractfactory.io/spec/33 and each definition futher expanded upon here: Monolithic Versioning Pattern <http://rfc.abstractfactory.io/spec/3> Polylithic Versioning Pattern <http://rfc.abstractfactory.io/spec/2> If you can find anything out of place, wrong or missing, here or at tech-artists would be an excellent place to discuss. Thanks Best, Marcus -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/18f7fdfd-d410-43e3-9f58-2e485face8b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
