Release plan: Difference between revisions

Jump to navigation Jump to search
m
no edit summary
mNo edit summary
Line 20: Line 20:


=== Detailed Time Schedule and Checklist ===
=== Detailed Time Schedule and Checklist ===
# Dec/Jun 17th: Development stream is declared "frozen" or "yellow".
# '''Dec/Jun 17th:''' Development stream is declared "frozen" or "yellow"
#:Send a mail to the flightgear-devel mailing-list to announce the state.
#:Send a mail to the flightgear-devel mailing-list to announce the state
#:change the content of wiki template at [[Template:GitStatus]] to <pre>{{GitStatus:frozen}}</pre>
#:Create a "release preperations" topic at the forum and make it a "Global Announcement"
# Jan/Jul 17th: Create new release branch, assign new version number to dev-stream, re-open streams
#:Change the content of wiki template at [[Template:GitStatus]] to <tt><nowiki>{{GitStatus:frozen}}</nowiki></tt>
# '''Jan/Jul 17th:''' Create new 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, declare the streams "closed" or "red"
##Send a mail to the flightgear-devel mail-list, asking not to commit/push anything, declare the streams "closed" or "red"
##change the content of wiki template at [[Template:GitStatus]] to <pre>{{GitStatus:closed}}</pre>
##Post an update to the forum topic
##Change the content of wiki template at [[Template:GitStatus]] to <tt><nowiki>{{GitStatus:closed}}</nowiki></tt>
##Bump up the version-number of simgear/next, flightgear/next and fgdata/master to an even number (2.5.0 -> 2.6.0)
##Bump up the version-number of simgear/next, flightgear/next and fgdata/master to an even number (2.5.0 -> 2.6.0)
##Compile and test drive FlightGear with the new version-number
##Compile and test drive FlightGear with the new version-number
Line 44: Line 46:
##:for flightgear and simgear: ''git push origin next''
##:for flightgear and simgear: ''git push origin next''
##:for fgdata: ''git push origin master''
##:for fgdata: ''git push origin master''
##: declare dev-streams "open" or "green"
##: Declare dev-streams "open" or "green"
##: change the content of wiki template at [[Template:GitStatus]] to <pre>{{GitStatus:open}}</pre>
##: Change the content of wiki template at [[Template:GitStatus]] to <tt><nowiki>{{GitStatus:open}}</nowiki></tt>
##:Send a mail to the flightgear-devel mailing-list to announce the state.
##: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 and ThorstenB for the OpenSuse build
## Trigger James for the Jenkins-builds and Curt for a snapshot release and ThorstenB for the OpenSuse build
# Feb/Aug 1st: Start preparing the release notes and a press announcement
# '''Feb/Aug 1st:''' Start preparing the release notes and a press announcement
# Feb/Aug 17th: Create binaries/installers, pack fgdata, publish files, announce new version, close the release-branch
# '''Feb/Aug 17th:''' Create binaries/installers, pack fgdata, publish files, announce new version, close the release-branch
##Tag the release/2.6.0 branches of simgear, flightgear and fgdata and push the tags.
##Tag the release/2.6.0 branches of simgear, flightgear and fgdata and push the tags.
##:for flighgear, simgear and fgdata: ''git tag version/2.6.0-final''
##:for flighgear, simgear and fgdata: ''git tag version/2.6.0-final''
Line 117: Line 119:
* Announce the new version to the public
* Announce the new version to the public
** Write a changelog: [[Changelog 2.6.0]]
** Write a changelog: [[Changelog 2.6.0]]
** Contact flightsim websites and send them/link them to a "press release"
** Contact flightsim websites and send them/link them to the "press announcement"


=== Open Items, Questions ===
=== Open Items, Questions ===

Navigation menu