FlightGear history: Difference between revisions

Jump to navigation Jump to search
release
(release)
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.
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}}
{{Main article|Release plan/Lessons learned#2016.1}}
Line 206: Line 206:
|-
|-
| April 4, 2017 || 2017.1.3 (bugfix release)
| April 4, 2017 || 2017.1.3 (bugfix release)
|-
| May 22, 2017 || 2017.2.1 (bugfix release)
|-
| September 20, 2017 || 2017.3.1
|}
|}


Line 224: Line 228:
|-
|-
| 2017.2 || Boston
| 2017.2 || Boston
|-
| 2017.3 || Prague
|}
|}


842

edits

Navigation menu