20,741
edits
FlightGear 3.0 backlog: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 4: | Line 4: | ||
{{WIP}} | {{WIP}} | ||
{{cquote|To get to the 3.0 goal sometime in the near future, it's probably a good idea to create a backlog of open items in the wiki and link the release | {{cquote|To get to the 3.0 goal sometime in the near future, it's probably a good idea to create a backlog of open items in the wiki and link the release plan document to that. | ||
plan document to that. | |||
As usual, we don't have to be perfect for a new major release number. But the new features being the reason for the new major number should | As usual, we don't have to be perfect for a new major release number. But the new features being the reason for the new major number should | ||
| Line 25: | Line 24: | ||
needed! (backed by Thorsten and Stuart) | needed! (backed by Thorsten and Stuart) | ||
=== Long-standing bugs === | |||
Then some fixes for long-standing, not really critical but annoying bugs | Then some fixes for long-standing, not really critical but annoying bugs | ||
* <del>the current rain system still only works for Basic Weather</del> {{Done}} (by Stuart for 2.10) | * <del>the current rain system still only works for Basic Weather</del> {{Done}} (by Stuart for 2.10) | ||
* turbulence should affect YaSim and JSBSim the same way | * turbulence should affect YaSim and JSBSim the same way [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40228.html] | ||
=== Eye Candy === | |||
Then maybe some cool, but not so important features to make things complete: | Then maybe some cool, but not so important features to make things complete: | ||
| Line 34: | Line 37: | ||
* windsocks moving with ground wind rather than wind at aircraft position | * windsocks moving with ground wind rather than wind at aircraft position | ||
Ideally, making full use of things we already have to present the best possible | Ideally, making full use of things we already have to present the best possible scenery | ||
scenery | |||
* regionalized random building types | * regionalized random building types | ||
| Line 41: | Line 43: | ||
* exploit the placement mask possibilities fully | * exploit the placement mask possibilities fully | ||
And then, ship 3.0 with (finally) the next edition of a world scenery release, | And then, ship 3.0 with (finally) the next edition of a world scenery release, so we can really present much better visuals! So, personally I'd like 3.0 to be a release that doesn't only have cool features, but also cool features which work basically everywhere and a release that doesn't have the current snags like 'this doesn't work with that, and the GUI is counter-intuitive and so on. | ||
so we can really present much better visuals! So, personally I'd like 3.0 to be | |||
a release that doesn't only have cool features, but also cool features which | |||
work basically everywhere and a release that doesn't have the current snags | |||
like 'this doesn't work with that, and the GUI is counter-intuitive and so on. | |||
Let me be the first to admit that it's much more fun doing my own stuff the way | Let me be the first to admit that it's much more fun doing my own stuff the way I like and then just merge it in. But if we can find consensus about any plan having to do with integration of new features and making it all work together, then I'm willing to reserve the majority of my coding time for working towards that goal. Would this be something to aim for in a 3.0 release? | ||
I like and then just merge it in. But if we can find consensus about any plan | |||
having to do with integration of new features and making it all work together, | |||
then I'm willing to reserve the majority of my coding time for working towards | |||
that goal. Would this be something to aim for in a 3.0 release? | |||
== Related Pages == | == Related Pages == | ||