Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Software Versioining: A Time Travel Problem in Software Engineering
Similar to Software Versioining: A Time Travel Problem in Software Engineering (20)
Recently uploaded
Recently uploaded (20)
Software Versioining: A Time Travel Problem in Software Engineering
- 1. SOFTWARE VERSIONING A Time Travel Problem in Software Engineering
- 2. Disclaimers - Some things may be opinionated and even controversial - They may even turn up to be wrong over time - I let them in to draw opinions and start conversations
- 3. Goals of Versioning • State identification • Qualifying and quantifying change • Marketing • Guidance for deployments
- 4. Branches and Versions, TBD ? 1 2 Release (Optional) Main Feature Maintenance (Optional)
- 5. If you thought that was bad …here is GitFlow
- 6. SCHEMAS • Single Component (1, 2, 3 …) • SemVer (1.2.3) • CalVer (20.04.1) • Exotic Schemas (such as Kalvin, eh)
- 7. SNAPSHOT-ing Release on every commit or Maven’s 1.0.2-SNAPSHOT?
- 8. Merge Conflicts • Feature Branches (short-lived in TBD) • Release Branches • Pull requests everywhere?
- 10. Tags and Digests • postgres, postgres: 12, postgres:12.5 • postgres:12.5@sha256:d233caaf92c611 4ccc1f903c578308e710a73a5fd36c15fe 0999c24a17e32ed1 • postgres@sha256:d233caaf92c6114ccc 1f903c578308e710a73a5fd36c15fe0999 c24a17e32ed1
- 12. Bundles and Dependencies • Same Problem • But with Many Dimensions • We are now travelling across “Inception”- style worlds
- 13. Combinatorial Explosion c1_v1 c1_v2 c2_v1 c2_v2 c3_v1 c3_v2 Count Triangles! 3 Microservices with 2 versions give 2^3 = 8 possible worlds for our product
- 14. Ways to Solve Address • Pruning Search Space • Adding More Automation • Versioning on Meta level (i.e., API) • Getting “Greedy” (i.e. always latest – I prefer less of that)
- 15. What we Want • Deploy by Digest • But know exact version deployed • And know whether it is safe to roll forward or roll back and to what • And for bundled context
- 16. You Are Not Alone No One is There Yet!
- 17. What I do (opinionated) • TBD, not GitFlow • Auto-increments via Conventional Commits on every push • Separate versioning schema for feature branches • Keep release branches on separate minors • Treat bundles atomically – linearize • Keep distance of supported versions short
- 18. About me, Pavel Shukhman • MCS from UIUC • CKA and CKAD certified • Working with Infrastructure, DevOps, DataOps for more than 10 years • Co-Founder and CEO of Reliza • Twitter: @taleodor • LinkedIn: pshukhman
- 19. Tool Reference • GitVersion - https://gitversion.net • Semantic Release - https://github.com/semantic- release/semantic-release • Release-it - https://github.com/release-it/release- it • Reliza Versioning - https://github.com/relizaio/versioning and Reliza Hub – https://relizahub.com
- 20. Thank You!
Editor's Notes
- What versioning schema(s) do you use and why?
- What versioning schema(s) do you use and why?
- Do you release on every commit or not and why?
- Have you encountered merge conflicts – what solutions did you use?
- Did you encounter this problem? What did you do to solve it?