2,732
edits
Red Leader (talk | contribs) (Start rewriting and cleanup) |
Red Leader (talk | contribs) (→Version numbers: Finish section) |
||
Line 78: | Line 78: | ||
== Version numbers == | == Version numbers == | ||
FlightGear version numbers consist of three digits, separated by dots: | FlightGear version numbers consist of three digits, separated by dots: | ||
=== Before 2016.1 === | === Before 2016.1 === | ||
* '''Major''' (<u> | * '''Major''' (<u>3</u>.4.0): Only increased after significant changes to the functionality of the software (e.g., 1.x.x → 2.0.0 (due to switch to [[OSG]]). | ||
* '''Minor''' ( | * '''Minor''' (3.<u>4</u>.0): Has two applications: | ||
** '''Stable releases''' always have ''even numbers'' (e.g. 2. | ** '''Stable releases''' always have ''even numbers'' (e.g. 2.8.0, 2.10.0, 2.12.0). | ||
** The ''' | ** The '''latest [[Git]] version''' or '''[[FlightGear build server|nightly build]]''' uses an ''odd number'', always one more than the latest stable release's minor revision numbere. For example, when the latest release was 3.4.0, the current development stream was 3.5.0. | ||
* '''Revision''' ( | * '''Revision''' (3.4.<u>0</u>): Increased by bugfix releases (e.g., 2.12.1). | ||
=== 2016.1 and after === | === 2016.1 and after === | ||
* ''' | * '''Year''' (<u>2016</u>.1.0): The year the version was released. | ||
* ''' | * '''Number''' (2016.<u>1</u>.0): Which release of the year the version is (note: starts at 1). | ||
* '''Revision''' (2016.1.<u>0</u>): Indicates one of | * '''Revision''' (2016.1.<u>0</u>): Indicates one of two things: | ||
** When a release | ** In the '''latest [[Git]] version''' or '''[[FlightGear build server|nightly build]]''', this digit is 0, indicating that it is unstable. | ||
** When a new '''release''' is created, this digit is set to 1. With bugfix that is made, this digit is increased by 1, and a new version created. | |||
{{note|In general, release are referred to by their first two digits (e.g., 3.4). However, when filing a bug report or debugging problems, it is a good idea to give the full release number.}} | {{note|In general, release are referred to by their first two digits (e.g., 3.4). However, when filing a bug report or debugging problems, it is a good idea to give the full release number.}} |