I also work for a large company with plenty of talented developers and thousands of production Apache-1.3 servers along with hundreds of custom Apache-1.3 modules. It will be years before I can even consider Apache2, given the architecture and API differences between the two. If something could be done in an Apache-1.4 and 2.1/2.2 to help bridge the gap perhaps one day Apache2 will be an option, but today it is simply too big a gap to jump and I am pretty sure the bulk of the Apache community is in the same boat.
I think the key thing is "bugfixes" compared to "features" and "architecture changes".
I am +1 on seeing bugfixes go into v1.3 - people are using it, and if it can work better, so be it. But to actively encourage people to add features or architecture changes to v1.3, that simply turns v1.3 into "something else no longer compatible with v1.3", which we already have: v2.0.
Regards, Graham --
