Elive versioning numbers assigned to releases

#1

The versions used in the Elive releases can be confusing for you, or maybe not! But in the end they wants to follow a specific logic based in common sense which I’ll explain here:

  • Wants to be logic and common sense as much as possible
  • Follows a linear increment based in the development & date
  • Numbers includes always 3 identifiers, like 3.0.3
    • The first number means the type of OS, like its codename, a major release, etc…
    • The second numbers marks a stated progress of the development
    • The third number is assigned to every new build, and can go from 1 to 99

Let’s say we have Elive 3.0.0 codenamed Opal released, every update that will receive will be assigned in the 3.0.xx number

There will be not any development further a stable release, only updates, fixes, and minor or needed improvements

Second number meaning:

The second number is an important one to understand, which since now will follow this practice:

  • x.0.x : stable / final release
  • x.7.x : alpha development: don’t expect to have it good working, needs your betatesting reports about hardware & drivers especially
  • x.8.x : beta development: don’t expect all the features working, but we need your betatesting reports about the ones that doesn’t works
  • x.9.x : release-candidate: versions that expects to be ready to use, betatesting is crucial here, we need to have everything working without problems

Difficulties by using other methods:

  • If you have 3.0.0 as stable, and you have a new alpha or beta build, naming it “3.0.1” will be confusing, same for “3.1.0”
  • If you have 3.0.0 stable released and you want to give it an update, which number you would give if not 3.0.1 ?
  • They are not intuitive for those who don’t understand the specific meaning
0 Likes