20,741
edits
Release plan: Difference between revisions
→2.10
(→2.10) |
(→2.10) |
||
| Line 201: | Line 201: | ||
** perform a sync with JSBSim sources before the feature freeze. | ** perform a sync with JSBSim sources before the feature freeze. | ||
** decide early on if/when navdata can be updated [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39280.html] | ** decide early on if/when navdata can be updated [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39280.html] | ||
** merge requests that didn't make it into the previous release should probably be handled early during the upcoming release cycle | ** merge requests that didn't make it into the previous release should probably be handled early during the upcoming release cycle | ||
** distro-specific repositories should probably be updated, too [http://flightgear.org/forums/viewtopic.php?f=42&t=18852&p=174943] | ** distro-specific repositories should probably be updated, too [http://flightgear.org/forums/viewtopic.php?f=42&t=18852&p=174943] | ||
| Line 209: | Line 207: | ||
** there are usually reviews posted on blogs, forums etc after each release - we should specifically collect links to those and evaluate all opinions [http://forum.avsim.net/topic/400897-my-experience-with-flightgear-210/] [http://forum.avsim.net/topic/399809-fg-210-most-certainly-a-new-era-of-fg/] | ** there are usually reviews posted on blogs, forums etc after each release - we should specifically collect links to those and evaluate all opinions [http://forum.avsim.net/topic/400897-my-experience-with-flightgear-210/] [http://forum.avsim.net/topic/399809-fg-210-most-certainly-a-new-era-of-fg/] | ||
** the release plan should be augmented for the sub-release procedures [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39710.html] | ** the release plan should be augmented for the sub-release procedures [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39710.html] | ||
** there were a number of navcache/SQLite related issues reported via the issue tracker and the forum/devel list [https://code.google.com/p/flightgear-bugs/issues/detail?id=894] [http://flightgear.org/forums/viewtopic.php?f=68&p=175690#p175690] [http://code.google.com/p/flightgear-bugs/issues/detail?id=1055] | |||
** a little irritation/frustration was caused due to the conflicting review statements concerning the new radio propagation code [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38905.html] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38825.html] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33692.html] - some of this boiled down to coding style related issues, highlighting the fact that different core developers have different "coding styles" and requirements when reviewing merge requests, because we still lack an official "FlightGear coding style guide" [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38958.html] | |||