Release Management

(TODO: Finish this....)

This page will describe how releases will be named and which naming convention is behind that.

Basically the Release number consist of the following part:

major.minor.patch[.bugfix]-RevNumber

Currently we have the major number 0, so this means everything can be changed....

I hope to stabelize the first things in 0.6.0 may be in 0.7.0

The plan is to have Major Release (x.0.0)

  • Major Release means

new features etc. may be break backwards compatibility and

  • Minor Release means

Minor releases can break backwards compatibility.
Changes allowed

  • New features
  • Bug fixes
  • Security fixes
  • Database migrations

This page will outline how releases will be handled
Major Release (x.0.0)

SupoSE currently doesn't has a Major releases (1.0.0).

  • Minor Release (0.x.0)

Minor releases can break backwards compatibility.
Changes allowed

  • New features
  • Bug fixes
  • Security fixes
  • Database migrations

Changes not allowed

None at this moment.

Patch Release (0.0.x)

Patch releases shouldn't break backwards compatibility.
Changes allowed

  • Simple new features
  • Bug fixes
  • Security fixes

Changes not allowed

  • New features with a lot of changes
  • Database migrations

Also available in: HTML TXT