371
edits
FlightGear Newsletter January 2012: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear Newsletter January 2012 (view source)
Revision as of 12:13, 1 February 2012
, 1 February 2012→2.6.0 release preparations
m (Unprotected "FlightGear Newsletter January 2012": Vivian will check for spelling ;)) |
|||
| Line 7: | Line 7: | ||
=== 2.6.0 release preparations === | === 2.6.0 release preparations === | ||
On January 17, the release branches were created from our [[Git]] repositories. From then on, no new features (and aircraft) shall be pushed. Only bug fixes are accepted. Development for the next release 2.8.0 started | On January 17, the release branches were created from our [[Git]] repositories. From then on, no new features (and aircraft) shall be pushed. Only bug fixes are accepted. Development for the next release 2.8.0 has already started. | ||
'''FlightGear 2.6.0 will be released on February 17!''' | '''FlightGear 2.6.0 will be released on February 17!''' | ||
==== Release candidates ==== | ==== Release candidates ==== | ||
In order to fix bugs we first need to identify them. That's | In order to fix bugs we first need to identify them. That's what we create release candidates for. These are basically complete releases, meant for testing by a large group of people. As the actual release is still some time away, bugs found during these tests have a fair chance getting fixed. Do note that the earlier bugs are reported, the more time we'll have to fix them. | ||
The release candidates are available [http://www.flightgear.org/news/flightgear-v2-6-release-candidates at our website]. Please help us create a release with a minimum amount of bugs! | The release candidates are available [http://www.flightgear.org/news/flightgear-v2-6-release-candidates at our website]. Please help us create a release with a minimum amount of bugs! | ||