Board index FlightGear The FlightGear project

2019.1 release

Questions about the FlightGear organisation, website, wiki etc.

2019.1 release

Postby legoboyvdlp » Sun Jul 28, 2019 10:39 pm

Just a notice that 2019.1 has at long last been released. It is available from:

https://sourceforge.net/projects/flight ... se-2019.1/

Notice that according to the release plans these releases are unstable. 2018.3.2 remains the last stable release.

On another note a 2018.3.3 release is expected tomorrow if all goes well bringing various bugfixes including fixes to the sounds when reloading model view, fixes to mapstructure, fixes to nasal in <load>, and most importantly METAR. This 2018.3 release will be the latest stable version.

I am not aware if Mapstructure is fixed in the 2019.1 release yet.

Thanks to Torsten and Bugman for getting this done!
User avatar
legoboyvdlp
 
Posts: 7003
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: 2019.1 release

Postby Octal450 » Mon Jul 29, 2019 3:49 am

If mapstructure isn't fixed I am still frustrated - as all airliners using glass cockpits are still broken.
But thanks Thorsten and Bugman for the release.

:(

Kind Regards,
Josh
I am a person.
User avatar
Octal450
 
Posts: 4388
Joined: Tue Oct 06, 2015 12:51 pm

Re: 2019.1 release

Postby bugman » Mon Jul 29, 2019 9:44 am

Note that all the minor point releases - assuming that 4 releases were to be made in the year that would be 2019.1.x, 2019.2.x, 2019.3.x, and 2019.4.x - are considered stable releases. It is just that the 3rd release of the year is designed to be a long-term stable release that will have extra efforts made to make it super stable prior to FSweekend, and it will probably have fixes backported to it for longer.

Josh, as you are deeply involved in development, there is a way you can significantly help in backporting fixes. If you can track fixes in the git repositories and take note of the git hashes involved, then you can help make sure that the fixes appear in the relevant releases. I'd suggest subscribing to the commitlogs mailing list (not to be confused with the FGAddon commitlogs mailing list). Then when a fix is pushed, you get to see all changes and hashes to the flightgear, simgear and fgdata repositories at the same point in time. I use filters to bypass and simplify my inbox. You can then respond to one of the commitlog messages (I've set the reply-to header so responses are sent by default to the development mailing list) and ask for the "Committer", rather than commit "Author", to cherry-pick hashes A, B, and C to branches X, Y, and Z. The core developers sometimes struggle to remember and track which changes should be backported so, if you had the motivation, you could really help the development process there. Just regularly kick the wheels and push for a fix to be backported and then push for Torsten to push his blue button once more ;) Although it sounds like nagging, tracking the status of fixes on multiple release branches is a very useful contribution.

Cheers,
Edward


Edit: The 3rd release of the year is also chosen as the long-term stable release as the tile containing the default airport, chosen at the start of the year, should by September be well developed and populated with many custom models.
bugman
Moderator
 
Posts: 1698
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: 2019.1 release

Postby yanfiz » Mon Jul 29, 2019 7:06 pm

Hello,

What is property tree of "Use disk cache for faster loading (DDS Texture Cache)" in "Rendering Options" to add it to custom settings?

Thank you.
yanfiz
 
Posts: 118
Joined: Fri Apr 03, 2015 2:27 am

Re: 2019.1 release

Postby yanfiz » Mon Jul 29, 2019 7:26 pm

I was probably in a hurry to ask :) I've found it.
yanfiz
 
Posts: 118
Joined: Fri Apr 03, 2015 2:27 am

Re: 2019.1 release

Postby Octal450 » Mon Jul 29, 2019 9:39 pm

Dear bugman - I wish I had the time to be involved and do this, but I simply do not. I have really busy life and barely have enough time for all my projects right now.

Kind Regards,
josh
I am a person.
User avatar
Octal450
 
Posts: 4388
Joined: Tue Oct 06, 2015 12:51 pm

Re: 2019.1 release

Postby bugman » Tue Jul 30, 2019 7:53 am

Josh, I realise you're frustrated. The bug fix that you are pushing for, does it exist? You keep mentioning the mapstructure error but, as far as I am aware, this is not fixed yet. But we shouldn't hold up all point releases and wait for this to be fixed and backported to the branches. That is a major reason - or simply 'the reason' - why the release process has been stalled this year. Instead of asking for all releases to stop, it would be more productive to wait for James to return from holidays (so he has time to work on a fix) and then help with the testing so that the bug can be properly eliminated, then James can backport the changes to the branches, and finally Torsten can push the release button once again. Remember the open source motto - release early and release often.

Regards,
Edward
bugman
Moderator
 
Posts: 1698
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: 2019.1 release

Postby legoboyvdlp » Tue Jul 30, 2019 9:17 am

Yes, it is fixed, for about a month now.
I will get the commit hashes for you later today. :)
User avatar
legoboyvdlp
 
Posts: 7003
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: 2019.1 release

Postby legoboyvdlp » Tue Jul 30, 2019 11:39 am

Just sent the hashes to the mailing list.
User avatar
legoboyvdlp
 
Posts: 7003
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: 2019.1 release

Postby bugman » Tue Jul 30, 2019 12:18 pm

Cheers! That's exactly what is needed to help push things along :) Well, monitoring that it does get backported and reminding developers once a week (or fortnight) can also help.

Regards,
Edward
bugman
Moderator
 
Posts: 1698
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: 2019.1 release

Postby Octal450 » Tue Jul 30, 2019 12:22 pm

Yes - it was fixed by Lego who I am very grateful spent alot of time working on code he was not responsible for.

I literally think now time is bring wasted. Instead of getting 2019.2 stable and out we are faffing around with 2018.3.3 for some reason I don't understand.

Kind Regards,
Josh
I am a person.
User avatar
Octal450
 
Posts: 4388
Joined: Tue Oct 06, 2015 12:51 pm

Re: 2019.1 release

Postby sidi762 » Tue Jul 30, 2019 1:34 pm

Octal450 wrote in Tue Jul 30, 2019 12:22 pm:Yes - it was fixed by Lego who I am very grateful spent alot of time working on code he was not responsible for.

I literally think now time is bring wasted. Instead of getting 2019.2 stable and out we are faffing around with 2018.3.3 for some reason I don't understand.

Kind Regards,
Josh


Hi Josh,

My understanding about 2018.3.3 is that we need to have a stable release for those who don't really know and cares about computer stuff, but the current stable version, 2018.3.2 is broken due to changes of NOAA. While 2019.1 contains some new features and is still considered unstable, 2018.3.3 is needed to maintain a stable version of FG so that people can fly happily with bug fixed instead of waiting for 2019.1.

Kind regards,
Sidi
sidi762
 
Posts: 127
Joined: Sat Jun 18, 2016 8:15 am
Location: Beijing, China
Callsign: DAG0762
Version: 2018.3.2
OS: MacOS Mojave

Re: 2019.1 release

Postby Octal450 » Tue Jul 30, 2019 1:47 pm

Clearly - somebody is getting delusional
Look here: https://sourceforge.net/projects/flight ... se-2019.1/

There is a new release - releases are supposed to be STABLE..... This is nonsense! At least make it a RC or something so people actually KNOW!

By this logic, I could make the A320 at V1.0 already even though he is missing many crucial features.

Kind Regards,
Josh
I am a person.
User avatar
Octal450
 
Posts: 4388
Joined: Tue Oct 06, 2015 12:51 pm

Re: 2019.1 release

Postby Thorsten » Tue Jul 30, 2019 1:59 pm

we are faffing around with 2018.3.3 for some reason I don't understand.


LTS release vs technical point releases.

Several people (including myself) have expressed the sentiment that they won't go through the typical release trouble (testing, feature announcements on the webpage, special bugfixing time) four times a year. As a result it was deemed reasonable to declare only one release (the year.3 one) a major long-term stable release which gets high testing and fixing effort from everyone in advance and gets bugfixes applied during the year till the next LTS release.

The technical releases have correspondingly less announcement and testing/bugfixing (and I have not looked at it at all and won't), so if you find e.g. the Shuttle doesn't run on 2019.1, I'm just going to point you to 2018.3 which I have tested and found working fine.

That's the idea here.

If you want to understand the reasoning in detail, I suggest to read up the discussion on the mailing list archives.
Thorsten
 
Posts: 10965
Joined: Mon Nov 02, 2009 8:33 am

Re: 2019.1 release

Postby Octal450 » Tue Jul 30, 2019 2:06 pm

I believe this policy is against the average user just to be convenient for developers. So now they need 2 versions. For example
The shuttle needs 2018.3 - but the IDG A32X need 2019.1. So now he needs 2 versions which do not friendly coexist.

This is nonsense and I'm loosing my patience with the attitude of not helping the users. It is our job as developers to help the users be able to use the software with ease. This is why GUIs exist instead of having only commandline.

Kind Regards,
Josh
I am a person.
User avatar
Octal450
 
Posts: 4388
Joined: Tue Oct 06, 2015 12:51 pm

Next

Return to The FlightGear project

Who is online

Users browsing this forum: No registered users and 16 guests