Release plan: Difference between revisions
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 == |
Revision as of 20:50, 9 February 2016
Current release: 2020.3.19 (18 Oct 2023) Next release: 2020.3.20 See release plan for details. |
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.
FlightGear has had two release plans over 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 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 lessons learned from previous releases.
General release concept
Version numbers
FlightGear version numbers consist of three digits, separated by dots:
Before 2016.1
- Major (3.4.0): Only increased after significant changes to the functionality of the software (e.g., 1.x.x → 2.0.0 (due to switch to OSG).
- Minor (3.4.0): Has two applications:
- Stable releases always have even numbers (e.g. 2.8.0, 2.10.0, 2.12.0).
- The latest Git version or nightly build uses an odd number, always one more than the latest stable release's minor revision numbere. For example, when the latest release was 3.4.0, the current development stream was 3.5.0.
- Revision (3.4.0): Increased by bugfix releases (e.g., 2.12.1).
2016.1 and after
- Year (2016.1.0): The year the version was released.
- Number (2016.1.0): Which release of the year the version is (note: starts at 1).
- Revision (2016.1.0): Indicates one of two things:
- In the latest Git version or nightly build, this digit is 0, indicating that it is unstable.
- When a new release is created, this digit is set to 1. With bugfix that is made, this digit is increased by 1, and a new version created.
Note In general, release are referred to by their first two digits (e.g., 3.4). However, when filing a bug report or debugging problems, it is a good idea to give the full release number. |
Detailed time schedule and checklist
- (On the 17th of the release month): The first Jenkins script is triggered to create
release/xxxx.x.0
branches with version xxxx.x.0. - Jenkins creates the binaries for xxxx.x.1.
- Patches going into the
release/xxxx.x.0
branch automatically trigger a new build with a increase of the revision version number (see above) and we immediately have a bugfix release. - On the
next
branch, the version number is changed. - Nightly builds are created from
next
after every push in that branch.
The process is repeated after a set number of months (to-be-decided).
Version files
- FGData
- fgdata/version
- SimGear
- simgear/version
- FlightGear
- flightgear/version
- FGRun
- fgrun/version
Bug tracking
The bugtracker is the primary source of bug reports. Unlike the forum or mailing list, bugs reported there will be tracked, making it easier for developers to. When reporting bugs, it is best to provide as muh information as possible to more easily find the bug.
Lessons learned
See Release plan/Lessons learned for a list of things that turned out well and should be kept for the next release as well as thing that didn't turn out so well and should be changed for future releases. Ideally, the release plan should be updated and augmented so that the lessons learned are incorporated accordingly.
Related content
Mailing lists
- Torsten Dreyer (Dec 17th, 2015). [Flightgear-devel] Release 3.8.