Astronomy/MeadeGeneric
1
0
Fork 0
Code Pull Requests Wiki Activity

Add How the version numbers work

Colin Dawson
2026-04-14 21:10:59 +00:00
parent 89cc177e3c
commit 4707b2cb6c
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
How-the-version-numbers-work.md
+17
@@ -0,0 +1,17 @@
version numbers are assigned by the Teamcity build server. The source code will produce an invalid version number and is never used for releases, or even for test versions that I've been known to give out from time to time. It's always a build from teamcity for any potential release.
The version number is split into four parts
major.minor.revsion.build
major - This is a major release of the driver and will be incremented when there is a major refactor of code. This could happen if I change the driver from COM based, to Alpaca, or if I change from .net Framework to .net core, for example.
minor - This will be upgraded when new features are added or there is a significant change to the code. Think adding a very significant upgrade to the driver code, for example if I add support for a whole new telescope, or a whole new set of features like fans, reticule eyepieces.
revision - This used for defect fixes, adding a minor feature enhancement and further builds of a given release whilst in development
build - this will be incremented for every build that takes place via the Teamcity pipeline and will be unique to each build.
Changes to the major, minor or revision will be done as part of the process of merging the develop branch into the master branch. Once that merge has completed and the build is successful on the master branch a new release will be added to the website, along with the details of the changes since the last merge.