185
edits
Release plan: Difference between revisions
→Bug tracking: minor spelling with some clarifications...
Red Leader (talk | contribs) (Add a table to help visualize) |
(→Bug tracking: minor spelling with some clarifications...) |
||
| Line 245: | Line 245: | ||
== Bug tracking == | == Bug tracking == | ||
The [http://sourceforge.net/p/flightgear/codetickets/ bugtracker] is the primary source of bug reports. Unlike the forum or mailing list, bugs reported there will be tracked, making it easier for developers to. When reporting bugs, it is best to provide as | The [http://sourceforge.net/p/flightgear/codetickets/ bugtracker] is the primary source of bug reports. Unlike the forum or mailing list, bugs reported there will be tracked, making it easier for developers to keep up with them. When reporting bugs, it is best to provide as much information as possible to more easily find the bug. If you can provide a backtrace, please do so and attach it to the bug report. When creating backtraces, please use "thread apply all bt full" at the gdb command prompt. | ||
<!-- | <!-- | ||
| Line 323: | Line 323: | ||
--> | --> | ||
== Lessons learned == | == Lessons learned == | ||
See [[Release plan/Lessons learned]] for a list of things that turned out well and should be kept for the next release as well as thing that didn't turn out so well and should be changed for future releases. Ideally, the release plan should be updated and augmented so that the lessons learned are incorporated accordingly. | See [[Release plan/Lessons learned]] for a list of things that turned out well and should be kept for the next release as well as thing that didn't turn out so well and should be changed for future releases. Ideally, the release plan should be updated and augmented so that the lessons learned are incorporated accordingly. | ||