Hi! Here comes my point which ist that of an outsider/user.
Yes, breaking compatibily sucks, so I'd say 2.1 seems like a god idea. But from what I read here it is just now wort the hassle. Why? The installed userbase of 2.0 is not large enough (with missing PHP/perl support and still evolving filter features). IMHO you may still break existing configs. It shouldn't get a habit but it's ok once or twice. Which, BTW, reminds me of the SSL config bug (SSLAcceptMutex options horked). That one has also possible backwards incompatibility. I suggest that someone (or a team) works on the new aaa architecture on his (their) own server. The result can than be dropped into the main dev when it is ready. But I would not change to much for 2.0 or it will have problems with distributors. I guess, endless rewriting install scipts for packages is a dull job ;-) Masi
