20,741
edits
FlightGear Newsletter April 2013: Difference between revisions
Jump to navigation
Jump to search
→Release-candidate builds for the 2.10.1 (bug-fix) release available
(→Development news: http://flightgear.org/forums/viewtopic.php?f=68&p=180697#p180697 http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39779.html) |
|||
| Line 9: | Line 9: | ||
=== Release-candidate builds for the 2.10.1 (bug-fix) release available === | === Release-candidate builds for the 2.10.1 (bug-fix) release available === | ||
As previously mentioned on the devel list[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39708.html], James is now attempting a 2.10.1 release, to see if this improves our perceived quality. There's some bug fixes we already aware of, including a Windows path-handling one which is quite significant. | |||
Now, the great news is that thanks to James' work, we are now able to crank out full installers right from the Jenkins build server. That will save us a bunch of downloading and hours of uploading for every new release candidate. | |||
Continuing with the experimental creation of a bug fix release for 2.10: | |||
* [http://flightgear.simpits.org:8080/job/Mac-release/ Mac OSX] | * [http://flightgear.simpits.org:8080/job/Mac-release/ Mac OSX] | ||
| Line 14: | Line 19: | ||
* [http://flightgear.simpits.org:8080/job/Linux-release/ Linux] | * [http://flightgear.simpits.org:8080/job/Linux-release/ Linux] | ||
These are the first Windows releases produced automatically (Jenkins creates the installer) instead of via Curt, so please be on the look-out for anything that seems messed up / omitted. Based on very limited testing via a Windows VM everything seems sane and the apps run. | These are the first Windows releases produced automatically (the Jenkins build server creates the installer) instead of via Curt, so please be on the look-out for anything that seems messed up / omitted. Based on very limited testing via a Windows VM everything seems sane and the apps run. | ||
The intention is that the quality of these builds is 'at least as good' as 2.10.0. We would be happy for them to replace 2.10.0 on the web sites as soon | |||
as they pass a collective sanity check from people here. | |||
If you find new bugs, that's fine, but unless they are regressions since 2.10.0 (which is unlikely, hopefully) then they should not block releasing; they can be fixed in a (hypothetical!) 2.10.2 or wait until 2.12. | |||
In particular the Windows builds include the UTF-8 pathname fix which is significant for various people. | In particular the Windows builds include the UTF-8 pathname fix which is significant for various people. | ||
| Line 22: | Line 30: | ||
In general we're looking for 'yes the build works' or 'you've forgotten to include XYZ' feedback, not 'random shader bug 123 is still not fixed. | In general we're looking for 'yes the build works' or 'you've forgotten to include XYZ' feedback, not 'random shader bug 123 is still not fixed. | ||
So if there's a bug that is (still) troubling you, update its entry in the [http://flightgear-bugs.googlecode.com/ issue tracker], help with finding a test case, or fire up an editor and fix it. | So if there's a bug that is (still) troubling you, update its entry in the [http://flightgear-bugs.googlecode.com/ issue tracker], help with finding a test case, or fire up an editor and fix it. | ||
=== Advanced Weather === | === Advanced Weather === | ||