> > One way to reduce the testing fragmentation we see in 1.5 would be to > move from having every new feature as a compile-time option that is > off by default to a strategy where most options that are deemed worthy > are compiled in and enabled for everyone. Given the limited > resources, I'm note sure the project has the luxury to support the > wide range of possible configurations that we see today in 1.5/head. > We should aim to get maximum compile-time and runtime exposure for > features so that everyone is compiling and testing other people's work > as much as possible. This could also have the interesting benefit of > sanitizing the code of the maze of ifdefs we see in there today. >
In principal, I agree; In practice I don't think we can make that happen until Windows and Unix share a stable release series. -- Derrick
