How To Choose Version Numbers - Semantic Versioning

Today we learn how to properly choose version numbers for packages and software. For this, we use semantic versioning.
Semantic Versioning: semver.org/
◾◾◾◾◾◾◾◾◾◾◾◾◾◾◾◾◾
📚 Programming Books & Merch 📚
🐍 The Python Bible Book: www.neuralnine.com/books/
💻 The Algorithm Bible Book: www.neuralnine.com/books/
👕 Programming Merch: www.neuralnine.com/shop
💼 Services 💼
💻 Freelancing & Tutoring: www.neuralnine.com/services
🌐 Social Media & Contact 🌐
📱 Website: www.neuralnine.com/
📷 Instagram: / neuralnine
🐦 Twitter: / neuralnine
🤵 LinkedIn: / neuralnine
📁 GitHub: github.com/NeuralNine
🎙 Discord: / discord

[@vektracaslermd743]

Very helpful, Florian. Versioning was something I always had only a crude understanding of. The major, minor, patch system makes perfect sense. Thanks for spelling it out!

[@ccc_ccc789]

I think you missed to teach how to create a software version using git tag and release notes containing the new feature and fix made or breaking changrs

[@aarons.6741]

Or a great idea for an extra video?💪

[@juliencarrier5252]

Thanks for this video ! i never tried to understand the logical under versioning. Now i understand

[@ragnarok9131]

You put a lot of hard work! Thankyou

[@dipeshsamrawat7957]

Thank you.

[@mak448a]

Could you cover Llama3/Dolphin-Llama on your channel?

[@MathGeniuses-xv6cl]

It was fun

[@viktorsheep]

If i update a minor version, should the patch be reset to 0?