* Like it used to be the case with detailed log files, most end users are usually very willing to help, but unable to provide backtraces - reconsider adding
the google breakpad support [http://flightgear.org/forums/viewtopic.php?f=17&t=20538&p=188028#p188017]
* under some circumsances, initial navcache/POI processing took up to 10 minutes, even on powerful Linux boxes with plenty of horsepower and RAM using just the default settings [http://flightgear.org/forums/viewtopic.php?f=18&t=20455&p=187432#p187417]
* the way we are incrementing version numbers in SG_SRC/FG_SRC and FGDATA seems to be causing issues ("base package check failed"), which were reported already during the last release cycles (all the way back to 2.8), even one core developer reported the issue during the 2.10 cycle (many people affected by this seem to be using brisa's download & compile script, but it doesn't appear to be Linux-specific, it also seems to happen on Windows). It seems fgdata version is 2.12 while the SG/FG source trees in next were still looking for 2.11 - could be also because of cmake caching, and the cache not being updated properly once certain files are touched in SG/FG source, still investigating... [http://flightgear.org/forums/viewtopic.php?f=22&t=20304&p=186647#p186647] [http://flightgear.org/forums/viewtopic.php?f=45&t=20467]. The problem seems to be [http://flightgear.org/forums/viewtopic.php?f=22&p=186942#p186942 this].