I spent a good chunk of today writing up some svn command line tools for managing updates, commits and so on based on properties. This is largely in an effort to avoid full out branching, allowing us to differentiate between more frequent development commits (to track changes during development) and less frequent production-ready commits. By ignoring any revisions of a file past the most recent “production ready” tagging when updating we can ensure development and production maintain the same basis while without adding anything to the development cycle. Project name tagging will also allow us to track obvious and hidden dependencies for the purpose of recompiling… We currently have little build environment to speak of despite working so closely to the data structure itself, so sanity checking and such is largely… and acquired skill. It is also entirely undocumented.

Once I have them spruced up a bit I’ll put them up.