Release plan: Difference between revisions

m
Saw the date and couldn't resist. enjoy...
mNo edit summary
m (Saw the date and couldn't resist. enjoy...)
Line 7: Line 7:


=== General Release Concept ===
=== General Release Concept ===
New FlightGear releases will be scheduled twice a year. The magic number to remember is 17 (we tried 42, but that didn't turn out so well. 17 is perfect: 1 is not a prime, 7 is a prime and so is 17). On the 17th of January (1) and July (7) a new release branch will be created for SimGear, FlightGear and FGDATA.  
New FlightGear releases will be scheduled twice a year. The magic number to remember is [http://itre.cis.upenn.edu/~myl/languagelog/archives/003951.html 17] (we tried 42, but that didn't turn out so well. [http://itre.cis.upenn.edu/%7Emyl/languagelog/archives/003949.html 17] is perfect: 1 is not a prime, 7 is a prime and so is [http://itre.cis.upenn.edu/%7Emyl/languagelog/archives/003946.html 17]). On the 17th of January (1) and July (7) a new release branch will be created for SimGear, FlightGear and FGDATA.  


After branching, we will allow one month for bug fixing in the release branch, so building and packing of the binaries and FGDATA will take place around February, 18th and August, 18th. Allowing a few days for distribution of the files, new versions should be publically available around the 20th of February and August.  
After branching, we will allow one month for bug fixing in the release branch, so building and packing of the binaries and FGDATA will take place around February, 18th and August, 18th. Allowing a few days for distribution of the files, new versions should be publically available around the 20th of February and August.  
929

edits