Search results

{{Release}} ...an is actually a continual work-in-progress, and is refined with every new release and how much available resource and interest there is.

...2.X, though there is no guarantee that all features listed will be in that release, or that it will be released in 2022! [[Category:Release plans]]

...to the FlightGear multiplayer Universe. With FGJobs, you can set up flight plans (jobs) and gain points for every successful completion. Note that every eve ** User defined: Players can set up flight plans, for example: Imagine you're on EDDB and you type <code>!job EDDM</code>. N

...nderstand the FlightGear development process|The development process]] · [[Release plan]]<br/> ...velopers|List of Core Developers]] · [[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projects]] <br/>

...and the FlightGear development process|Le processus de développement]] · [[Release plan|Plan de parution]]<br/> [[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projets]] · [[Request for comme

...e release (aka ‘LTS preview’) in a few weeks time. The upcoming stable FG release (2020.2) still works with CMake 3.0 <ref>https://sourceforge.net/p/flightge The default airport for this release with be BIKF.

...r's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch wit ...e by at least a month. This will provide sufficient time to distribute the release candidates and process end-user feedback.

...ion, such as the c172p, we may also want to check for criteria listed at [[Release:Aircraft Selection Criteria]]. * An aircraft release is packaged into a .zip, possibly with a renamed file extension - the zip i

...ount of work by the developers over the last year. As you can see from the release [http://www.flightgear.org/version.html version summary], there have been a Since the last release, FlightGear has improved dramatically with such things as ultra-realistic [

...rstand the FlightGear development process|Il processo dello sviluppo]] · [[Release plan|Piano dei rilasci]]<br/> ...velopers|List of Core Developers]] · [[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projects]] <br/>

[[#FlightGear v3.6 release|FlightGear v3.6 release]]<br/> === FlighGear v3.6 release ===

...and infrastructure changes that that will be in the next long term stable release (LTS), but receive less testing and some aircraft maybe incompatible. Pleas ...are harder to pick up. One of the strengths of opensource 'release early, release often', needs reporting to work. As a general point, it is less work to mak

...bly a good idea to create a backlog of open items in the wiki and link the release plan document to that. As usual, we don't have to be perfect for a new major release number. But the new features being the reason for the new major number sho

{{Disclaimer|id=final-fixed-function-release}} ===2020.3.11 release ===

[[#New ATC-pie release|New ATC-pie release]]<br> [[#New version scheme and release preparations|New version scheme and release preparations]]<br>

[[#New ATC-pie release|New ATC-pie release]]<br/> === New ATC-pie release ===

== Submit your work plans and schedule your activities == ...|Start of construction with runways and taxiways. Planning also has future plans for terminals and modeling.

{{Mergeto|2022.X Release Plan}} ...been working on carriers since April 2020; originally the intention was to release as part of the 2020.2 LTS however the changes have grown into a set of new

{{Disclaimer|id=final-fixed-function-release}} ...0 update .26 FG 2021.x preview release plans|April newsletter]]. As usual, plans can change and progress depends on the availability of contributors (includ

{{Disclaimer|id=final-fixed-function-release}} ...0 update .26 FG 2021.x preview release plans|April newsletter]]. As usual, plans can change and progress depends on the availability of contributors (includ