#2157 major version shenanigans: 2018.3.4 <> 2019.1.1 <> 2019.1.2

[Mathias Homann]

Please update the flightgear.org website to properly indicate which of the three existing releases is the one that people are actually supposed to use.
on flightgear.org: 2019.1.1
on sourceforge: 2018.3.4
on the github mirror: 2019.1.2 (but no datafile exists anywhere)

[Slawek Mikula]

Agreed. There is some nice explanation in: https://forum.flightgear.org/viewtopic.php?f=28&t=36694#p358555. Mathias can you provide me the link to the github mirror you mentioned above ?

[Slawek Mikula]

I've created small list of things that should be corrected on websites:

• sourceforge download page (https://sourceforge.net/projects/flightgear/files/): change the readme and maybe change naming conventions with different folders e.g. release-2018.3-LTS or something like that or release-2019.1-unstable
• wiki template (http://wiki.flightgear.org/Template:GitStatus) to indicate what version is stable and what version is unstable
• website - https://www.flightgear.org/- change information on the main welcome page to indicate which versions are stable and whis is not. There is a big banner with 2019.1.1. There is no mention in the announcements of 2018.3.4 version which is marked as a main on the SF page.
• website - download section - https://www.flightgear.org/download/ - add info about 2018.3.4 as a stable one and mark 2019.1.1 as a unstable release (not to mention formatting issues)

[Mathias Homann]

I guess nothing has been done here?

fligthgear.org still lists 2019.1.1 as the relevand version, here on sourceforge it is still 2018.3.4...
oh and the github version is 2019.1.2: https://github.com/FlightGear/flightgear/releases

so please can someone clean up this mess?

[James Turner]

I think the fastest solution is to update the website to explain that 2019.1.x is an interim (unstable) release, and that 2018.3.4 is still the latest official release. Unfortunately only a couple of people can update the website content (and I'm not one of them), so I'll email them to suggest that,

[Lars Toenning]

Closing this at it seems to be fixed on the website.