735
edits
Release plan: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
{{Release}} | {{Release}} | ||
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 and how much available resource and interest is | 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 and how much available resource and interest there is. | ||
[[File:ReleasePlan.jpg|thumb|250px|The original release plan.]] | [[File:ReleasePlan.jpg|thumb|250px|The original release plan.]] | ||
| Line 9: | Line 9: | ||
* Subsequently a release plan was developed by Mathias Fröhlich, Martin Spott, Thorsten Brehm and Torsten Dreyer during [[LinuxTag]] 2011. | * Subsequently a release plan was developed by Mathias Fröhlich, Martin Spott, Thorsten Brehm and Torsten Dreyer during [[LinuxTag]] 2011. | ||
* A more regular plan was proposed by Torsten Dreyer after the 3.6 release was [[FlightGear Newsletter November 2015#FlightGear v3.6 canceled|cancelled]]. | * A more regular plan was proposed by Torsten Dreyer after the 3.6 release was [[FlightGear Newsletter November 2015#FlightGear v3.6 canceled|cancelled]]. | ||
* Currently "Long Term Support" (LTS) releases are generated every ~24 months, with intermittent "preview" between them. | * Currently "Long Term Support" (LTS) releases are generated every ~24 months, with intermittent "preview" releases between them which receive less testing and support. | ||
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. However, do not underestimate the amount of effort go create a new release! Most of the burden falls on a few people. | 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. However, do not underestimate the amount of effort go create a new release! Most of the burden falls on a few people. | ||
| Line 33: | Line 33: | ||
## The version files are incremented. | ## The version files are incremented. | ||
## Builds are generated. | ## Builds are generated. | ||
# When a new LTS preview is declared (after ~ | # When a new LTS preview is declared (after ~12 months): | ||
## A release branch is cut from "next". E.g. release/2022.1 | ## A release branch is cut from "next". E.g. release/2022.1 | ||
## The version files are incremented. | ## The version files are incremented. | ||
## Builds are generated for the preview LTS. | ## Builds are generated for the preview LTS. Testing of aircraft against these releases is strongly encouraged. | ||
## Additional branches are created for subsequent releases from the original release branch (e.g. release/2022.1 -> release/2022.2) | ## Additional branches are created for subsequent releases from the original release branch (e.g. release/2022.1 -> release/2022.2) | ||
## Fixes are merged into the release branch as well as "next" | ## Fixes are merged into the release branch as well as "next" | ||
## Further builds and release are generated until an LTS is declared (e.g release/2022.3) | ## Further builds and release are generated until an LTS is declared (e.g release/2022.3). | ||
## fgaddon is branched and a new catalog generated. | |||