8,567
edits
FlightGear Newsletter November 2011: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter November 2011 (view source)
Revision as of 19:07, 1 December 2011
, 1 December 2011Note about aircraft during frozen Git
No edit summary |
(Note about aircraft during frozen Git) |
||
| Line 12: | Line 12: | ||
{{Main article|Release plan}} | {{Main article|Release plan}} | ||
On December 17, our [[Git]] repository will be declared "frozen". This means that 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 December 17, our [[Git]] repository will be declared "frozen". This means that 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. | ||
Contrary to the last release cycle, 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. 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. | |||
Keep in mind that the people that are able to commit your stuff are just as busy finishing their own work as you are! Therefore it is important that you create merge requests for everything that you'd like to see included in the upcoming release, as soon as possible. This includes new aircraft and large updates to existing aircraft. | Keep in mind that the people that are able to commit your stuff are just as busy finishing their own work as you are! Therefore it is important that you create merge requests for everything that you'd like to see included in the upcoming release, as soon as possible. This includes new aircraft and large updates to existing aircraft. | ||