Django's API Stability Policy

Django 1.0 took so long to arrive because there was, I guess, this idea that 1.0 was the moment when the backwards compatibility guarantees would really kick in. We want to make sure we had all of the everything in place the way we wanted it. And after a while, it became clear that that was kind of a fool's errand that the APIs will never be perfect. So that's on point. We just said, yeah, it's time to do 1.0 now. But I don't recall a lot of changes or discussions around changing that policy. My memory is we pretty much always had that intent of giving a couple of releases before changing something