Menu
▾
▴
#194 FG2.2.0 Release blockers
Done
nobody
None
2018-09-30
2010-12-02
Anonymous
No
Originally created by: zakalawe@mac.com
Originally owned by: zakalawe@mac.com
Meta-bug to track bugs blocking the next release of FlightGear
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Blockedon: 192
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Blockedon: 177
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Cc: frbouvi
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Cc: -frbouvi durktals
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Jester is planning to update the terrasync libsvn usage, to avoid keeping a second copy of the data locally - i.e a 50% reduction in the disk footprint of terra-sync-ed files. This would obviously be good to have for the release, and should be easy to test (or indeed, revert) since terrasync is self-contained. This doesn't constitute a blocker, but if it's read in time, I would strongly advocate including it.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Blockedon: 197
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Ridding a few more NaN sources for the release would be good. When a proper solution for #198 isn't ready in time, at least an easy workaround could be used (changing several default values).
Blockedon: 198
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Adding bug 200 as a blocker - been broken for a while, but blocks the A380 and several other complex models from working correctly on Mac, at least.
Blockedon: 200
Related
Tickets:
#200View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
(No comment was entered for this change.)
Blockedon: 204
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
We don't want to explain every new user why there are options in our menus that don't work.
Blockedon: 174
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Removed #198 as a blocker since a single change for YASim won't help much. YASim integration requires a larger overhaul (see comment at #198). Also see YASim issues #178, #47, 202. Would still be good for the release if s.o worked on all these issues (I won't :) ). Anyone maintaining the YASim (or FDM) integration in general right now?
Blockedon: -198
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
(No comment was entered for this change.)
Blockedon: 110
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
removing 193 as a blocker - it's not a real bug, more a build/documentation issue that can trip people up.
Blockedon: -193
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Blockedon: 213
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
oops, typo (213=>231)
Blockedon: -213 231
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
Issue 236 may also block, as --use-custom-scenery-data=true is default in preferences.xml
Blockedon: 236
Related
Tickets:
#236View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Fixing #253 may also be worthwhile for the release.
Blockedon: 253
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
As the c172p is the default aircraft and especially used for comparing the different sims and their fdm it could be also worth to add #213?!
Blockedon: 213
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Fix for #184, #47 is also a 2.2.0 candidate, if no new problems are reported.
http://www.gitorious.org/fg/flightgear/commit/32b69f823abd9d9adf99c2cf9aa6bf98f5f780bb
Blockedon: 184
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Adding issue 222 as a blocker. Several patches are already availabe in fg/next.
When tests are successful, these should be merged to fg/2.2.
Blockedon: 222
Related
Tickets:
#222View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
adding 266
Blockedon: 266
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Issue 266 may only affect FG GIT - not FG2.2.0 (maybe caused by the recent FDM/tank update). Needs to verified. Not a blocker unless 2.2.0 is affected...
Related
Tickets:
#266View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Tested issue 266 - doesn't affect the 2.2.0 branch. => unblocking :)
Blockedon: -266
Related
Tickets:
#266View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Fix available for issue 252 - another candidate?
Blockedon: 252
Related
Tickets:
#252View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
There you are ;)
Since the C172P is our default aircraft, I'd say a bug in its autopilot is a release-blocker. Not sure if it is a real bug though (cannot test it right now, so feel free to give it a go).
Blockedon: 270