20,741
edits
Release plan: Difference between revisions
→2.10: http://flightgear.org/forums/viewtopic.php?f=18&t=19745
(→2.10) |
(→2.10: http://flightgear.org/forums/viewtopic.php?f=18&t=19745) |
||
| Line 213: | Line 213: | ||
** 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] | ** 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] | ** 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] | ||
** according to Windows users, the installer created by jenkins could use some optimizations [http://flightgear.org/forums/viewtopic.php?f=18&t=19745] | |||
* '''Better bug reports and troubleshooting''': | * '''Better bug reports and troubleshooting''': | ||