2,732
edits
Release plan: Difference between revisions
Jump to navigation
Jump to search
Move quote to general release concept for now
Red Leader (talk | contribs) (→Version files: Add FGRun) |
Red Leader (talk | contribs) (Move quote to general release concept for now) |
||
| Line 1: | Line 1: | ||
{{ | {{GitStatus}} | ||
The '''release plan''' is the process by which a new version of [[FlightGear]] is released. The release plan is actually a continual work-in-progress, and is refined with every new release. | |||
[[File:ReleasePlan.jpg|thumb|250px|The original release plan.]] | |||
FlightGear has had two release plans over [[FlightGear History|history]]. The original release plan was developed by Mathias Fröhlich, Martin Spott, Thorsten Brehm and Torsten Dreyer during LinuxTag 2011. The current plan was proposed by Torsten Dreyer after the 3.6 release was [[FlightGear Newsletter November 2015#FlightGear v3.6 canceled|cancelled]]. | |||
To suggest improvements and/or changes to the release plan, it is recommended to get in touch via the [[mailing list]]. Improvements can be based on the [[Release plan/Lessons learned|lessons learned]] from previous releases. | |||
== General release concept == | |||
{{FGCquote | {{FGCquote | ||
|1= Hi Everybody, | |1= Hi Everybody, | ||
| Line 49: | Line 57: | ||
}} | }} | ||
}} | }} | ||
<!-- | |||
== General release concept (old release plan) == | == General release concept (old release plan) == | ||
New FlightGear releases are scheduled twice a year. The magic number to remember is 17. On the 17th of January (the first month) and July (the seventh month), a new release branch is created for [[SimGear]], the FlightGear source, and [[fgdata]]. | New FlightGear releases are scheduled twice a year. The magic number to remember is 17. On the 17th of January (the first month) and July (the seventh month), a new release branch is created for [[SimGear]], the FlightGear source, and [[fgdata]]. | ||
| Line 76: | Line 74: | ||
The development stream of [[SimGear]], FlightGear, and fgdata is set into a frozen state one month before the branch-day (17th), to let the dust of development settle and to allow fixing the most annoying bugs in the code. During this period, developers should not add any new features, subsystems, and the like. Immediately after the stream has branched for the release, development in the main stream (next/master) is open for major changes until one month before the next branch-day. This results in a duty cycle of 5 month developing and 1 month thinking. | The development stream of [[SimGear]], FlightGear, and fgdata is set into a frozen state one month before the branch-day (17th), to let the dust of development settle and to allow fixing the most annoying bugs in the code. During this period, developers should not add any new features, subsystems, and the like. Immediately after the stream has branched for the release, development in the main stream (next/master) is open for major changes until one month before the next branch-day. This results in a duty cycle of 5 month developing and 1 month thinking. | ||
--> | |||
== Version numbers == | == Version numbers == | ||