Release plan: Difference between revisions

Jump to navigation Jump to search
m (moved Release Plan to Release plan: We never capitilize titles.)
Line 19: Line 19:
The Major version number will be increased after significant changes to the functionality of the software.
The Major version number will be increased after significant changes to the functionality of the software.


=== Detailed Time Schedule ===
=== Detailed Time Schedule and Checklist ===
# Dec/Jun 17th: Development stream is declared "frozen" or "red".
# Dec/Jun 17th: Development stream is declared "frozen" or "red".
# Jan/Jul 17th: Create new Release branch, assign new version number to dev-stream
#: Send a mail to the flightgear-devel mailing-list to announce the state.
# declare dev-stream "open" or "green", create binaries for RC0 from release-branch
# Jan/Jul 17th: Create new release branch, assign new version number to dev-stream, re-open streams
# Feb/Aug 17th: Create binaries/installers, pack fgdata, publish files, announce new version, declare release-branch "closed"
##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-streams "open" or "green"
##:Send a mail to the flightgear-devel mailing-list to announce the state.
## Trigger James for the Jenkins-builds and Curt for a snapshot release
# Feb/Aug 17th: Create binaries/installers, pack fgdata, publish files, announce new version, close the release-branch
##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.  
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