On 13 Dec 2009, at 22:10, Jacob Burbach wrote: > Nan errors still abound, sound system has lots of rough edges still, > the new material system is not finished, route manager not finished, > etc, etc. Even if everything could be cleaned up by then, there would > be no time left for any real testing/bug fixing. Seems like a bad idea > to me. Or would it be a release candidate type thing? Has development > even been frozen and branched yet?
One observation - the intention, at least mine and Tim's, is to move to quarterly releases, so I have no intention of 'finishing' the route manager for a particular release. (Regular release cycles take the pressure of rushing to complete a feature) Stable features will be integrated onto the 'next' branch, when they're complete (or a functionally useful subset is complete). The shaders and sound changes both fall into this category, while the route manager work is certainly not in that category yet. Bug-fixing, testing, etc is of course a separate issue - namely that fixing bugs is a lot less fun than writing features. James ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
