![]() ![]() bug fixes have been ported back to it and are being worked on as they are solved.Ģ018.2.0 is the "next" branch of the code. after that, it is up to us (TINU) to exercise the product and report any problems.Ģ018.1.1 is still in RC status. developers will generally make sure the updates compile and don't exhibit any glaring errors. that's slowed down a bit as the developers have gotten more and more busy with their real life jobs and families. i've got freeware and paidware stuff here that used to get updated almost every week. if a feature is not ready, it is simply rolled back until after the release and then rolled back in. As it was a third party issue this time that has put it back wasn't it? Was it servers being upgraded or moving addresses at github or Jenkins or something like that? Lets put it another way "How many updates to any FREEWARE program would you expect in a year?" Also PAIDWARE you are lucky to get maybe 2 updates a year!!! So maybe be a little more realistic on updates like 2 instead of 4!!! THIS IS NOT MEANT AS AN ATTACK ON THE TEAM This is just a point of view, I am more than happy with Flightgear Just don't see the point of the team pulling their hair out trying to meet deadlines.more so when they have other commitments in life, Such as a fulltime job, Family, and their sanity! All that to one side keep up the good work EVERYONE on the the Flightgear Team and thank you for a wonderful simulator!!! Welcome to the rolling updates world.Obviously some major issues still with this release (First instalment of the 2018 versions) as it is now running about 6 weeks behind schedule (of launch date) any sort of ideas of the ballpark date of release yet? It's just an idea.But how about just two releases a year instead of four One in January and one in July maybe, As then there is less pressure on everyone within the team, and it gives enough time to test the release before the date "due" Also it will take into account any third party issues that may arise. especially now as the launcher is evolving. ![]() anyone running 2018.2 right now is running bleeding edge alpha code. it will become 2018.2.1 when it gets to that point. Obviously some major issues still with this release (First instalment of the 2018 versions) as it is now running about 6 weeks behind schedule (of launch date) any sort of ideas of the ballpark date of release yet? It's just an idea.But how about just two releases a year instead of four One in January and one in July maybe, As then there is less pressure on everyone within the team, and it gives enough time to test the release before the date "due" Also it will take into account any third party issues that may arise.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |