FlightGear history: Difference between revisions

FlightGear history (view source)

Revision as of 14:52, 31 May 2018

586 bytes added , 31 May 2018

→‎Release timeline: update 2018.2's release date

Wkitty42

185

edits

@@ Line 45: / Line 45: @@
 Following the cancellation of 3.6, the modern FlightGear team revised the release plan and process. New releases are essentially selected and tuned "nightlies" instead of special compilations.
-Also, in this release the concept of rotating default airports first started. Suddenly, all FlightGear releases after 2016.1 have unique default airports and 'codenames'.
+Also, in this release the concept of rotating default airports first started. All FlightGear releases after 2016.1 have unique default airports and 'codenames'.
 {{Main article|Release plan/Lessons learned#2016.1}}
@@ Line 206: / Line 206: @@
 |-
 | April 4, 2017 || 2017.1.3 (bugfix release)
+|-
+| May 22, 2017 || 2017.2.1 (bugfix release)
+|-
+| September 20, 2017 || 2017.3.1
+|-
+| April 11, 2018 || 2018.1.1
+|-
+| May 22, 2018 || 2018.2.1
 |}
 == Cycled default airports ==
+FlightGear did not start changing the default airport until version 2016.1 was released. At that time, the idea was that each new release would have a new default airport. This chart lists the default airports since 2016.1 was released.
 {| class="wikitable"
 |-
-! Release !! Default Airport
+! Release !! ICAO !! Default Airport
+|-
+| 2016.1 || [[KSFO]] || San Francisco ''(transition)''
 |-
-| 2016.1 || San Francisco ''(transition)''
+| 2016.2 || [[LEBL]] || Barcelona
 |-
-| 2016.2 || Barcelona
+| 2016.3 || [[SBRJ]] || Rio de Janeiro
 |-
-| 2016.3 || Rio de Janeiro
+| 2016.4 || [[LSZH]] || Zürich
 |-
-| 2016.4 || Zürich
+| 2017.1 || [[ENBR]] || Bergen
 |-
-| 2017.1 || Bergen
+| 2017.2 || [[KBOS]] || Boston
+|-
+| 2017.3 || [[LKPR]] || Prague
+|-
+| 2018.1 || [[PHNL]] || Honolulu
+|-
+| 2018.2 || [[PHNL]] || Honolulu
 |}