User Tools

Site Tools


content:servalmesh:version_numbering

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
content:servalmesh:version_numbering [20/08/2013 00:07]
Andrew Bettison mention master branch
content:servalmesh:version_numbering [22/08/2013 01:23]
Andrew Bettison add more information and links to some release procedure pages
Line 1: Line 1:
 ====== Version numbering ====== ====== Version numbering ======
  
-[[.:]] uses a //major//.//minor//[.//bugfix//] [[http://en.wikipedia.org/wiki/Software_versioning|version numbering scheme]]:+[[.:]] uses a //major//.//minor//[.//bugfix//] [[http://en.wikipedia.org/wiki/Software_versioning|version numbering scheme]] intended for human consumption:
   * the //major// number increases (resetting //minor// and //bugfix// to zero) to signal a major technological advance or incompatibility with prior versions;   * the //major// number increases (resetting //minor// and //bugfix// to zero) to signal a major technological advance or incompatibility with prior versions;
   * the //minor// number increases (resetting //bugfix// to zero) to indicate an improvement compatible with recent versions;   * the //minor// number increases (resetting //bugfix// to zero) to indicate an improvement compatible with recent versions;
   * the optional //bugfix// number increases to indicate a bug fix with no new features, superseding all versions in the same major.minor number.  The //bugfix// number is implicitly zero ''.0'' if absent, and starts at ''.1'' for the first bugfix release.   * the optional //bugfix// number increases to indicate a bug fix with no new features, superseding all versions in the same major.minor number.  The //bugfix// number is implicitly zero ''.0'' if absent, and starts at ''.1'' for the first bugfix release.
  
-The currently released version number is defined by the latest release tag in the //master// branch of the [[https://github.com/servalproject/batphone|batphone GitHub repository]], and can be discovered using [[:content:dev:git]]:<code> +==== The 0.x series ====
-$ cd /tmp +
-$ git clone -q git@github.com:servalproject/batphone.git +
-$ cd batphone +
-$ git describe --match '[0-9].*' origin/master +
-0.91 +
-+
-</code>+
  
-This number should coincide with the latest version downloadable from [[https://play.google.com/store/apps/details?id=org.servalproject&hl=en|Google Play]] and from [[http://developer.servalproject.org/files/|Dreamhost FTP]].+The version numbers with major number zero **0.x** were the prototype phase of the [[.:]] project: 
 +  * protocol compatibility was not preserved between minor versions 
 +  * upgrades did not always work --- sometimes an un-install, re-boot and manual removal of files and folders was necessary 
 +  * the software was clearly marked as EXPERIMENTAL 
 +  * the release documentation and procedures were not formalised until the last few minor versions 
 + 
 +==== The 1.x series ==== 
 + 
 +The [[.:releases:version_1_0]] signalled the start of an upgradeable, protocol-compatible series of **1.x** releases. 
 + 
 +==== More information ==== 
 + 
 +  * [[.:releases:]] is a list of all releases to date and planned for the future. 
 +  * [[.:release:Discover the release status]] has instructions on how to discover the version number of the most recent release using [[:content:dev:git]]. 
 +  * [[.:release:Choose a new version number]] describes when and how version numbers are increased.
  
-  * If the GitHub release number is **higher** than the downloadable versions, that most probably means the last release's APK was simply not uploaded.  The next release can proceed as usual, and the world will simply miss out on a version of the software. 
  
-  * If the GitHub release number is **lower** than the downloadable versions, then something is seriously wrong and a senior developer should investigate. 
content/servalmesh/version_numbering.txt · Last modified: 22/08/2013 01:23 by Andrew Bettison