A different way to visualise version tags in git flow is to work backwards from managing the support experience to releases to deployments to testing to development to design.
When aiming for a single instance of any specific version tag across the entire repository to be the single-source-of-truth … it can get interesting when we theoretically consider the implications of master branches versus feature branches and continuous pipeline processing.
Yes, it is very likely that I choose too much complexity to encompass for my git flow pipeline. Time will tell as this infographic evolves, while doing the WordPress plugin development.
A big thank you to Gary Pendergast
& Shawn Wernig for sharing their experiences about leveraging version numbers for runtime environments and support discussions.
Leave a Reply