Joost de Heer wrote:
'Breaking a config file' is IMO that you can't just copy your 2.0 config file and it works. And the new mod_auth(n|z) structure just did that: A 2.0 config file needed changes to work in 2.2.
Certainly. These changes happened over a year ago; they were relegated on trunk to land in the next minor update for this very reason - the developers agreed this shouldn't happen to a user between 2.0.x and 2.0.y, and that the appropriate time would be between 2.0.x and 2.2.0. So alphas and betas were announced for 2.1.x several times so that users could provide feedback. Based on that very same ruleset, we won't break users once they configure 2.2.0 such that they can't simply bump to 2.2.x. Bill
