Asi es! La version 1.0 de Django va a ser lanzada y con algunas nuevas features!

Para saber mas a parte de los detalles de aca abajo pueden entrar en el Google Group de Django donde encontraran las maybe features y las not features

Tambien esta el schedule! Paciencia!

Recien el 10 de julio van a poder hacer un svn-update y empezar a probar los new-forms admin.

Must-have features
——————

1. “newforms-admin“.

It’s clear from discussion on this list that most consider a release without
“newforms-admin“ to be a bad idea. Further, “newforms-admin“ is nearly
done; we’ve already started talking about merging it to trunk.

2. Replacement of “oldforms“ throughout Django.

Nothing in Django 1.0 should rely on the deprecated “oldforms“ package.
We’ll need to replace “oldforms“ usage in generic views, and in
“django.contrib.auth“

“django.contrib.comments“ still uses “oldforms“ as well, but there’s
special situation here; see below.

3. Making Django 100% WSGI compliant.

This simply involves fixing ticket #285. We’ve delayed doing this to avoid
the backwards-incompatible change, but we must make this change before 1.0.

Dejo un texto de Adrian Holovaty

I think we ought to call the release 2.0.

Jacob and I have talked in the past about how we should’ve called
magic-removal version 1.0. (This ended up being 0.95.) For all intents
and purposes, it *was* 1.0 in spirit — it was the first major
refactoring of several parts of the framework, and it was a point for
me personally where I started to feel like an acceptable number of the
legacy warts from pre-open-sourcing had been removed.

So, that’s one reason: philosophically, conceptually, in our minds, in
our hearts, we’re really dealing with a 2.0 product. We know Django
rocks (and is rock-solid), and we should give it an appropriate
number.

My second reason for choosing 2.0 is, shall we say, less wholesome.
After having endured a 2.5+ year deluge of “When is 1.0 coming out?”
blog entries, comments, e-mails and in-person confrontations from
people all around the world, I would find it incredibly satisfying, in
a devilish way, to release this thing and slap a “2.0″ on it. It would
underscore the project’s stability while at the same time
demonstrating that version numbers are completely arbitrary.