Closed DewGew closed 6 years ago
I guess its best to change from 2.3 > 2.4 only when we add a new module or new functionalitity. When fixing bugs, you change it from 2.3.7 to 2.3.8 (2.3.9, 2.3.10, 2.3.11 etc)
Simpliest is to use Semantic Versioning e.g: Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes.
Next time I'll correctly update version.txt. :)
My understanding of the working method: With every PR we update version.txt; Existing 'last change' is added under 'changelog'. 'Last change' is updated with a description of the new PR.
Is this correct?
What are the guidelines for version numbering? When do we change the version number to 2.4?