Release plan: Difference between revisions

Line 202: Line 202:
** 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]
** 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]
** the "FlightGear & friends" SuseStudio images should probably be also updated for each release cycle [http://susestudio.com/a/sBTdmU/flightgear-friends--2]


* '''Better bug reports and troubleshooting''':
* '''Better bug reports and troubleshooting''':