sqlite's oo api

Hello internals, after SQLite's commit ~16hours ago i was reminded that i have violated vertain rules - not change something while in release process and not changing api's of non experimental extensions. I must admit i knew this before but i was in a conflict and i am still. The conflict is i want consistency and there was a decision for studlyCaps. To honor the rules more or less i first contacted the relevant ppl in private and the majority agreed to the change (so i didn't rally wait to hear all). Obviously i was a bit too hastily here. But i only started to workout the change because SQLite's OO API was never released other than in RC1 - and well that it was released like it was is of cause my failure as mentioned already. As you know my actings started a long discussion and now i am questioning: Are we following our rules and decisions? And if so which rule/decision do ppl want me to follow? The one i did which potentially hurts some article writers? Or the other one which would lead to a revert and inconsistency? For the moment my decision is to revert await the outcome of the ongoing discussion. Asked as one of the maintainers i still want the studlyCaps for consistency. Asked for PHP i also want the studlyCaps. It was a big mistake not to change the api right after the decision - as i said my fault. Sorry for the inconvenience Best regards, Marcus The full diff to get SQLite in studlyCaps fashion can be downloaded here: http://marcus-boerger.de/php/ext/sqlite/sqlite-oo-api-studlycaps.diff.txt