Release plan: Difference between revisions

→‎Version numbers: do not use major for first ánd second digit ;-)
(→‎Version numbers: do not use major for first ánd second digit ;-))
Line 14: Line 14:


=== Version numbers ===
=== Version numbers ===
* '''Major releases''' always have '''even numbers''' as the second version element, i.e. 2.6.0, 2.8.0, 3.0.0.
FlightGear version numbers exist of three digits, seperated by dots:
* '''Bugfix releases''' increase the least significant digit: 2.8.1, 2.8.2, 2.8.3.
* '''Major''' (<u>2</u>.4.1): is only increased after significant changes to the functionality of the software, i.e. 1.X.X => 2.0.0 (due to switch to OSG).
* The '''development stream''' (''latest Git version'') uses an '''odd number''', increasing the second element of the latest stable release's version by 1: (latest release is 2.8.0 =&gt; current development stream is 2.9.0, next official release is 3.0.0).
* '''Minor''' (2.<u>4</u>.1): has two applications:
* The major version number is increased after significant changes to the functionality of the software (i.e. FG 1.x => 2.0 due to switch to OSG).
** '''Stable releases''' always have ''even numbers'', i.e. 2.6.0, 2.8.0, 3.0.0.
** The '''development stream''' (''latest Git version'') uses an ''odd number'', increasing the minor number of the latest stable release's version by one. I.e., when the latest release is 2.8.0, the current development stream is 2.9.0.
* '''Revision''' (2.4.<u>1</u>): is increased by bugfix releases, i.e. 2.8.1, 2.8.2, 2.8.3.


=== Detailed time schedule and checklist ===
=== Detailed time schedule and checklist ===