Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Changes

Jump to: navigation, search

Release plan

996 bytes added, 15:24, 10 July 2011
Detailed Time Schedule
The Major version number will be increased after significant changes to the functionality of the software.
=== Detailed Time Schedule and Checklist ===
# Dec/Jun 17th: Development stream is declared "frozen" or "red".
#: Send a mail to the flightgear-devel mailing-list to announce the state.# Jan/Jul 17th: Create new Release release branch, assign new version number to dev-stream, re-open streams##Send a mail to the flightgear-devel mail-list, asking not to commit/push anything##Bump up the version-number of simgear, flightgear and fgdata to an even number (2.3.0 -> 2.4.0)##Compile and test drive FlightGear with the new version-number##Commit the new version number to next (flightgear+simgear) and master(fgdata)##Create the release branches on simgear, flightgear and fgdata named release/2.4.0##On the next/master branches, bump up the version-number of simgear, flightgear and fgdata to an odd number (2.4.0 -> 2.5.0)##Compile and test drive FlightGear with the new development version number##Commit the changes of version-number to next/master##Push the branches next/master and release/2.4.0 upstream## declare dev-stream streams "open" or "green", create binaries ##:Send a mail to the flightgear-devel mailing-list to announce the state.## Trigger James for RC0 from releasethe Jenkins-branchbuilds and Curt for a snapshot release# Feb/Aug 17th: Create binaries/installers, pack fgdata, publish files, announce new version, declare close the release-branch "closed"##Tag the release/2.4.0 branches of simgear, flightgear and fgdata.
From step 1) to step 2), no new features or major changes shall be pushed onto the development stream (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues.

Navigation menu