My store is trying to formalize the release management process for the OSS product that we support (editing: using SVN for version control). This is a kind of web development / CMS framework, including the product on which other projects are built. This gives a clear idea of ββthe version control system, which is especially critical for developers who use this tool.
I hope to find some examples of how best to graph this system so that we can better communicate with it and with external developers. I know that there are many standards and best practices in the field of version control, so I hope this applies to some kind of visual vocabulary. As one example, there is an excellent schedule at http://en.wikipedia.org/wiki/Versioning#Software_Versioning_schemes . Are there any guides on how these types of things should be designed?
version-control versioning project-management release-management visualization
Alex gilbert
source share