first of all this has nothing to do with a "power play". it has to do with a simple fact that betas are meant to be stable releases that users can develop against without worrying much about us pulling stuff from under them.
from the list i gather there is a large number of users that are waiting for a beta before they start upgrading their projects for the above reason. second of all, yes i was the advocate. i was trying to find a way to solve the problems everyone were complaining about. i found away, i proposed it, we had a discussion and a vote. we all voted +1. now that i had a chance to extensively use the api i dont think it was worth it and so i started the discussion again. it will take another vote where everyone votes to resolve this. i have two large projects on trunk, so i think i am affected more then others by this rollback with regards to hours of work. so take that back. -igor On 3/8/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> why put a beta out if a huge api break is coming??? i will change my vote to > -1 on releasing 1.3beta if we decide to fold the model refactor into it. I don't find that kind of power play to be very constructive, especially not because you are largely responsible for the 2.0 controversy (after being the greatest advocate for the change in the first place, and now the greatest advocate of reverting it). It's simple, if you want dropping 2.0 to happen you have to go through some pain too. If 2.0 stays, the models don't have to go in 1.3. Eelco
