Hi Michael,
I agree - we (the core team) have been extremely lax on effectively
communicating the status of the release. We certainly could have
handled the period between 1.1beta1 and today much better. I promise
we'll try to do better next time around.
Here's where we:
Django v1.1 is, for all intents and purposes, complete. Yes - people
are assigning bugs to the v1.1 milestone, but from a procedural point
of view, they aren't holding up the milestone.
The intention is to cut a release candidate (RC1) in the next day or
so, the purpose of which is to formally freeze strings for
translation. The intention is that about a week after the RC, we will
update all the translations that have been provided, and cut 1.1
final.
So - we should have v1.1 by the end of the month.
Again - apologies for the bad communication on our part, and thanks
for your understanding. I hope the final result is worth it.
Yours,
Russ Magee %-)