|Current release: (6 Nov 2020)|
Next release: 2021.1 (-181 days from now)
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.
General release concept
|Month||Number in cycle|
|January||4 (previous year)|
FlightGear version numbers consist of three digits, separated by dots:
- 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:
- 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:
|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.0branches with version xxxx.x.0.
- Jenkins creates the binaries for xxxx.x.1.
- Patches going into the
release/xxxx.x.0branch automatically trigger a new build with a increase of the revision version number (see above) and we immediately have a bugfix release.
- On the
nextbranch, the version number is changed.
- Nightly builds are created from
nextafter every push in that branch.
The process is repeated after a set number of months (to-be-decided).
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 keep up with them. When reporting bugs, it is best to provide as much information as possible to more easily find the bug. If you can provide a backtrace, please do so and attach it to the bug report. When creating backtraces, please use "thread apply all bt full" at the gdb command prompt.
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.
- Torsten Dreyer (Dec 17th, 2015). [Flightgear-devel] Release 3.8.