Wiki ⇒ The Project ⇒ Versioning system ⇒ CPG Dragonfly™ CMS
WikiThe Project ⇒ Versioning system

2. 1: Versioning system Parent
How Dragonfly’s versioning system works, and what you can expect each version to contain.

The versioning system is widely used by a lot of software and is a standard in most C, C++, Pascal, Delphi, etc. editors. It normally consists of 4 numbers, but we use 3 numbers and a string/number to show what the release contains.
A version is broken out as follows:

Major . Minor . Release . Build

We will try to explain all aspects of each part so that you will understand if a release is important for you.
  1. Major

    This number ONLY changes when something huge happens like a complete new way to call/control modules (thru classes for example) or only working on PHP5 due to the new way PHP5 handles classes. So don't expect this to happen soon or within a year.

  2. Minor

    This number changes more frequently and could rise up once or more in 1 year. It's also possible that within 1 year this number doesn't rise.
    The number increases when something huge inside a default module or core changes like: added function, edited theme template files, new theme template files or a new way how a module works. This happens mostly inside and DOESN'T affect the system heavily and an upgrade should work 98% of the time.

  3. Release

    Once a month we try to release a new package which will contain all significant bug fixes that are made that month. If there are no significant bug fixes in the month then we don't release it. Also, when we release a version with a "minor" increased number, this version will NOT be released and will start at 1 again (like 9.0.5 -> 9.1.1).

  4. Build

    These are mainly very important or unimportant releases depending on the number/string it contains. An explanation follows:

    1. SFx (Security Fix x)
      Can be released anytime and is announced with a news message and inside your administration panel since it concerns a security issue which could be high/low risk and is actually a "must have" for everyone.
    2. RCx (Release Candidate x)
      Release candidates are mostly put out as a stable release and are meant to test if you can upgrade without problems. Since it's not an official final stable release it could contain issues/bugs.
    3. PRx (Preview Release x)
      Some people really want to know how the new system will work/look and want to see it in action even while it is still buggy. This is for them.
    4. number like (0)
      Nothing bad just a mark in the finals like

Created: Wednesday, January 26, 2005 (00:30:32) by DJMaze
Updated: Thursday, April 03, 2008 (03:27:34) by tuta