Release plan: Difference between revisions

Jump to navigation Jump to search

Release plan (view source)

Revision as of 20:43, 12 December 2015

188 bytes added ,  12 December 2015
Some updates, mostly importantly add note about future changes to release process
(A bit of cleanup in the first paragraph)
(Some updates, mostly importantly add note about future changes to release process)
Line 1: Line 1:
{{Note|As of Decemeber 2015, the release plan is in the process of being changed so that the description below will no longer be accurate. See also [[Release plan/Lessons learned#3.60|Release plan/Lessons learned § 3.60]].}}
{{GitStatus}}
{{GitStatus}}


Line 96: Line 98:


== To bump up the version number ==
== To bump up the version number ==
* [https://gitorious.org/fg/fgdata FGData]
* fgdata
** edit the ''version'' file
** edit the {{fgdata file|version|t=version}} file
* [https://gitorious.org/fg/simgear SimGear]
* SimGear
** edit the ''version'' file
** edit the {{simgear file|version|t=version}} file
* [https://gitorious.org/fg/flightgear FlightGear]
* FlightGear
** edit the ''version'' file
** edit the {{flightgear file|version|t=version}} file
* [https://gitorious.org/fg/fgrun FGRun]
* FGRun
** edit the ''version'' file
** edit the [http://sourceforge.net/p/flightgear/fgrun/ci/next/tree/version version] file


== Definition of repository states ==
== Definition of repository states ==
Line 134: Line 136:


== Bug tracking ==
== Bug tracking ==
The [http://flightgear-bugs.googlecode.com bugtracker] will be our primary source for the bug fixing period. Bugs reported on the mailing list or forum will not be tracked! Reporters shall be requested to file a bug report at the bugtracker. Bugs shall be assigned a priority and a keyword to make the assignment to a developer easier. Bug reports that can't be confirmed or need more input from the reporter to get fixed will be assigned a new state "stalled" and only processed after more information has been provided. Bugs assigned a high priority will be downgraded, if no progress has been made over a certain amount of time. This is to prevent the release from being blocked by a bug that no developer is able (or willing) to fix. The only exception is "does not compile for one of the major platforms", which certainly is a release-blocker.
The [http://sourceforge.net/p/flightgear/codetickets/ bugtracker] will be our primary source for the bug fixing period. Bugs reported on the mailing list or forum will not be tracked! Reporters shall be requested to file a bug report at the bugtracker. Bugs shall be assigned a priority and a keyword to make the assignment to a developer easier. Bug reports that can't be confirmed or need more input from the reporter to get fixed will be assigned a new state "stalled" and only processed after more information has been provided. Bugs assigned a high priority will be downgraded, if no progress has been made over a certain amount of time. This is to prevent the release from being blocked by a bug that no developer is able (or willing) to fix. The only exception is "does not compile for one of the major platforms", which certainly is a release-blocker.


Bugs that were present in the latest stable release, and now considered "fixed", should be assigned a milestone label, corresponding with the upcoming stable release number. By doing so, they'll end up in [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=label%3AMilestone-2.12.0 the list of fixed bugs].
Bugs that were present in the latest stable release, and now considered "fixed", should be assigned a milestone label, corresponding with the upcoming stable release number. By doing so, they'll end up in [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=label%3AMilestone-2.12.0 the list of fixed bugs].
Line 142: Line 144:
The following table should be updated and augmented after each release, according to the [[Release plan#Lessons learned|Lessons learned]] section below.
The following table should be updated and augmented after each release, according to the [[Release plan#Lessons learned|Lessons learned]] section below.


{|class="wikitable"
{| class="wikitable"
!
! Stage
! width="500px" | Task
! width="500px" | Task
! Owner(s)
! Owner(s)
! Status for [[Changelog 2.12|2.12]]
|-
|-
! rowspan="7" |  
! rowspan="7" | Preparation
| Announce the state-change of the dev-streams, '''cross-post to JSBSim list''' (see lessons learned!)
| Announce the state-change of the dev-streams, '''cross-post to JSBSim list''' (see lessons learned!)
| TorstenD
| TorstenD
|
|-
|-
| Create/maintain the git branches
| Create/maintain the git branches
| TorstenD
| TorstenD
|
|-
|-
| Track the bugs on the tracker, trigger developers, adjust bug-priorities
| Track the bugs on the tracker, trigger developers, adjust bug-priorities
Line 162: Line 161:
| Sync the language files so they can be translated
| Sync the language files so they can be translated
| ThorstenB, James
| ThorstenB, James
|
|-
|-
| Beta testing  
| Beta testing  
Line 169: Line 167:
| Update documentation: [[FAQ]], [https://www.gitorious.org/fg/getstart/ The Manual], wiki
| Update documentation: [[FAQ]], [https://www.gitorious.org/fg/getstart/ The Manual], wiki
| Stuart, Gijs and anyone else
| Stuart, Gijs and anyone else
|
|-
|-
| Pack RC and final version of FGDATA
| Pack RC and final version of fgdata
|
|
|-
|-
Line 183: Line 180:
| Windows
| Windows
| Curt
| Curt
|
|-
|-
| MacOS
| MacOS
| Tat/James
| Tat/James
|
|-
|-
| Distribute files to download servers
| Distribute files to download servers
| Curt
| Curt
|
|-
|-
! rowspan="3" | Make adjustments on the web-site
! rowspan="3" | Make adjustments on the web-site
Line 199: Line 193:
| Generate aircraft page
| Generate aircraft page
| Curt, Gijs
| Curt, Gijs
|-
|-
|-
| Tag the [http://wiki.flightgear.org/index.php?title=Talk:Next_newsletter&action=edit&section=45 newsletter template] according to the released version
| Tag the [http://wiki.flightgear.org/index.php?title=Talk:Next_newsletter&action=edit&section=45 newsletter template] according to the released version
Line 206: Line 199:
|-
|-
! rowspan="2" | Announce the new version to the public
! rowspan="2" | Announce the new version to the public
| Write a changelog: [[Next Changelog]]
| Write a changelog: [[Next changelog]]
| All developers/contributors
| All developers/contributors
|-
|-
| Contact flightsim websites and send them/link them to the "press announcement". See [[release promotion]] for a list of already-contacted and yet-to-contact websites/magazins.
| Contact flightsim websites and send them/link them to the "press announcement". See [[release promotion]] for a list of already-contacted and yet-to-contact websites/magazines.
| '''EVERYBODY'''
| '''EVERYBODY'''
|}
|}
Line 216: Line 209:
* Automate and/or document the creation of RC's: "We need to get this automated some day. Or at least documented...(another one from "famous last words": if you have to do it more than once, automate it. If you can't automate it, document it."<ref>{{Cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39205.html |title=<nowiki>Re: [Flightgear-devel] Release candidates</nowiki> |author=Torsten Dreyer |date=29 January 2013}}</ref>
* Automate and/or document the creation of RC's: "We need to get this automated some day. Or at least documented...(another one from "famous last words": if you have to do it more than once, automate it. If you can't automate it, document it."<ref>{{Cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39205.html |title=<nowiki>Re: [Flightgear-devel] Release candidates</nowiki> |author=Torsten Dreyer |date=29 January 2013}}</ref>
* <del>Automate the creation of Windows and Mac installers</del>  {{Done}} <ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40650.html</ref> (see [[FlightGear Build Server]])
* <del>Automate the creation of Windows and Mac installers</del>  {{Done}} <ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40650.html</ref> (see [[FlightGear Build Server]])
* Automate the creation of FGDATA distribution
* Automate the creation of fgdata distribution
* Possibly try to find a way to automate testing of updated jsbsim code, so that the chance for breakage is reduced by running scripted tests <ref>{{Cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39109.html |title=<nowiki>Re: [Flightgear-devel] [Jsbsim-devel] JSBSim Synch with FlightGear</nowiki> |author=Torsten Dreyer |date=13 January 2013}}</ref><ref>{{Cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40201.html |title=<nowiki>Re: [Flightgear-devel] JSBSim Synch with FlightGear</nowiki> |author=Anders Gidenstam |date=11 June 2013}}</ref><ref>
* Possibly try to find a way to automate testing of updated jsbsim code, so that the chance for breakage is reduced by running scripted tests <ref>{{Cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39109.html |title=<nowiki>Re: [Flightgear-devel] [Jsbsim-devel] JSBSim Synch with FlightGear</nowiki> |author=Torsten Dreyer |date=13 January 2013}}</ref><ref>{{Cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40201.html |title=<nowiki>Re: [Flightgear-devel] JSBSim Synch with FlightGear</nowiki> |author=Anders Gidenstam |date=11 June 2013}}</ref><ref>
{{Cite web |url=http://sourceforge.net/p/flightgear/mailman/message/31762085/
{{Cite web |url=http://sourceforge.net/p/flightgear/mailman/message/31762085/
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/90585"

Navigation menu