----- > "Bill Stoddard" <[EMAIL PROTECTED]> writes: > > -1 (not a veto) > > > > With the release of a major application (Apache 2.0), the APR API should > > not change unless > > there is a compelling reason. This is not a compelling reason. > > Sure, it can wait, no problem. > > However, I can see how this situation might start to get painful for > APR developers, as more and more applications use APR. Apache 2.0 is > just one of N dependents; is there some reason Apache's release > process should affect the rate of APR development for everyone?
Breaking API compatability is not something that should be taken lightly. This is an issue with all users of APR, not just the http server. I am not against the API changing if there is a compelling reason for it. This change is light-years from compelling. Bill
