> I think people like him are asking: when is the fiddling done, and people
> have a program they can start to incorporate into their operating system
> releases, deploy for production customers, etc? While we're still working
> on low-level issues like pools/sms in APR and fixing other big performance
> issues, we're not there yet.
Another spin on the same question: when do the core developers (you know who
you are) think that the internal APIs have stabilized enough so that effort
expended porting home-grown modules won't need to be thrown away when 2.0
settles down?
Some of us (I don't have enough data to say "many") can't put the server
through heavy burn-in without local modules, and can't justify porting those
to a not-settled set of core APIs.
Or did I miss the announcement that we had passed this point? It doesn't
need to be an unbreakable promise, just some guidance.
