8,567
edits
FlightGear Newsletter May 2013: Difference between revisions
Jump to navigation
Jump to search
→Release preparations
No edit summary |
|||
| Line 6: | Line 6: | ||
== Development news == | == Development news == | ||
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]]. | Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]]. | ||
=== Release preparations === | |||
Following the [[release plan]], the FlightGear repositories will close for major changes on June 17. In this "frozen" state, no new features or major changes shall be pushed onto the development streams (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches on July 17. | |||
It's a good idea for aircraft developers to adhere to this rule. However, aircraft in fgdata may be handled as an exception from the frozen state. Any change to aircraft may be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Also, aircraft defined as part of the base package (e.g. the c172p) enter the frozen state and shall not undergo major changes in that period. | |||
=== Aircraft Checklists === | === Aircraft Checklists === | ||