8,564
edits
FlightGear Newsletter June 2012: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (Protected "FlightGear Newsletter June 2012" ([edit=sysop] (indefinite) [move=sysop] (indefinite))) |
No edit summary |
||
| Line 17: | Line 17: | ||
=== 2.8.0 release preparations === | === 2.8.0 release preparations === | ||
{{Main article|Release plan}} | {{Main article|Release plan}} | ||
Since the feature freeze on June 17, no new features may be pushed to our [[Git]] repositories. Aircraft outside the base package can still receive updates till July 17, when release branches will be created from the repositories. That is basically the birth of a new release. From then on only bug fixes will be accepted. | Since the feature freeze on June 17, no new features may be pushed to our [[Git]] repositories. Aircraft outside the base package can still receive updates till July 17, when release branches will be created from the repositories. That is basically the birth of a new release. From then on only bug fixes will be accepted. | ||
Release candidates are available from [http://www.flightgear.org/download/ flightgear.org/download], allowing (and encouraging) everyone to test the new version and report bugs at [http://flightgear-bugs.googlecode.com our bug tracker]. | |||
Thanks to the branching, development for the next-next release (3.0.0?) can start right away; even before 2.8.0 is released. | Thanks to the branching, development for the next-next release (3.0.0?) can start right away; even before 2.8.0 is released. | ||
| Line 31: | Line 33: | ||
}} | }} | ||
Emilian updated the signs textures to have some shading on top, which improves the overall appearance a lot. Also, Now it is possible to make use of new special types, such as {critical}, {safety}, {no-entry} and {hazard}. See the [[Signs| | Emilian updated the signs textures to have some shading on top, which improves the overall appearance a lot. Also, Now it is possible to make use of new special types, such as {critical}, {safety}, {no-entry} and {hazard}. See the [[Signs|signs article]] for more details. | ||
James was able to improve the rendering code considerably. The signs are now rendered per stg file into one geometry. This reduces the amount of geodes a lot. | James was able to improve the rendering code considerably. The signs are now rendered per stg file into one geometry. This reduces the amount of geodes a lot. | ||
| Line 43: | Line 45: | ||
{{cquote|I have been working on a 4-color incremental mark/sweep collector with the intention of merging it into the Nasal interpreter. | {{cquote|I have been working on a 4-color incremental mark/sweep collector with the intention of merging it into the Nasal interpreter. | ||
The work so far can be found at http://github.com/chrisforbes/incgc. There's still quite a lot to do, but the path is clear.|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37579.html Chris Forbes]}} | The work so far can be found at http://github.com/chrisforbes/incgc. There's still quite a lot to do, but the path is clear.|[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37579.html Chris Forbes]}} | ||
== Snapshot releases == | |||
Every now and then, easy-to-install development snapshots are created (usually, twice monthly). These snapshots depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker]. | |||
The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. | |||
== New software tools and projects == | == New software tools and projects == | ||