WEBVTT

00:00:00.000 --> 00:00:06.000
What can a version number such as 2.4.1 tell you?

00:00:06.000 --> 00:00:13.000
When a project follows SemVer, the three numbers describe kinds of API change.

00:00:13.000 --> 00:00:18.000
Read the version with the release notes.
6 semantic-versioning basics.

00:00:18.000 --> 00:00:30.000
Read major, minor and patch
A normal SemVer release has three number components.
Major version · Minor version · Patch version

00:00:30.000 --> 00:00:42.000
Major can break compatibility
It indicates a breaking change to the declared public API.
Public API · Incompatible change · Upgrade planning

00:00:42.000 --> 00:00:54.000
Minor adds compatible features
It adds functionality while preserving API compatibility.
Added functionality · Compatible API · Release notes

00:00:54.000 --> 00:01:06.000
Patch is for compatible fixes
It fixes incorrect behaviour without breaking the public API.
Bug fix · Compatible API · Patch release

00:01:06.000 --> 00:01:18.000
Early versions need extra care
Under SemVer, a zero major version is initial development.
Version 0.x · Initial development · API may change

00:01:18.000 --> 00:01:30.000
Check the project convention
Not every product follows SemVer; read its own release guidance.
Version policy · Release notes · Relevant project tests

00:01:30.000 --> 00:01:39.000
Your checklist
Read major, minor and patch · Major can break compatibility · Minor adds compatible features · Patch is for compatible fixes · Early versions need extra care · Check the project convention

00:01:39.000 --> 00:01:47.000
Version numbers help; release notes and testing still matter.
jerseyweb.je