FlightGear Newsletter July 2011: Difference between revisions

Jump to navigation Jump to search
m
add new section titled SNAPSHOT RELEASES (now also part of the template for future newsletters - stored at Talk:Next newsletter )
m (added template from Talk:Next newsletter - if you want to fix/improve this, please first change the template - thanks)
 
m (add new section titled SNAPSHOT RELEASES (now also part of the template for future newsletters - stored at Talk:Next newsletter ))
Line 5: Line 5:


== Development news ==
== Development news ==
== Snapshot releases ==
Some of you might know that James and Gene have spent a lot of time assembling a "nightly build server" for the FlightGear project: [[FlightGear Build Server]].
This monitors the git repository for any source code changes and then spawns builds for windows, linux, and the mac.
You can find the build server here: http://flightgear.simpits.org:8080/
This is really great work and a huge contribution to the FlightGear project.
Unfortunately, to run a nightly build from the build server, you still have to pull the latest data tree from the git repository. That's not all that hard once you work through the details, but it's a bit "fiddly" for some folks.
So Curt has been playing around with creating a developer's snapshot release which would be similar to our official release.
It's one big setup.exe that includes all the programs and the data. We are hopeful that this will eventually make the current development version of FlightGear more accessible for "joe average" users which would then in term hopefully give us more feedback and bug reports ahead of our official release.
None of this would be possible without the "hudson" build server that Gene and James set up.
There are a couple things that are done with this snapshot package:
* a unique app name of the form: FlightGear YYYYMMDD is assigned so you can have multiple versions installed concurrently and they don't step on each other and don't step on the official release. If people maintain multiple snapshots installed on their systems, that might help narrow down when a bug was introduced.
* The openal installer "oalinst.exe" is included and vcredist_x86.exe ... neither of these may be required in the long term if we can just ship the needed dll's, but that probably needs further testing.
Does it basically work? Are there any major packaging blunders? Please note, FlightGear bugs and feature request should still be handled through normal channels. But I am interested in packaging issues right now.
To provide feedback please us this forum thread: http://flightgear.org/forums/viewtopic.php?f=28&t=10488
For downloads please see:
* http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Win32/Setup%20FlightGear%20v20110629.exe"
== Nasal for newbies ==
== Nasal for newbies ==
== New software tools and projects ==
== New software tools and projects ==

Navigation menu