Hi all,
Those of you that have been paying attention to the Django release
roadmap [1] will have noticed that the original estimated release date
for Django 1.2 final has passed, but we haven't actually made a final
release.
Although Django aims to follow a date-based release cycle, we won't
make a release that we know contains major bugs. Therefore, we need to
push back the final release date for Django 1.2.
There are currently 120 bugs logged against the 1.2 milestone. Many of
these bugs are minor or longstanding errors. Over the next few days,
the core team will be examining this ticket list, leaving only the
tickets that:
* reveal a significant flaw in a feature added during the 1.2 cycle, or
* have the potential to cause catastrophic data loss.
Any bug that doesn't meet one of these criteria will be taken off the
1.2 milestone. We won't forget about these issues -- they'll still be
in Trac, and we'll address them in a later release.
We're sensitive to the fact that during the Django 1.2 release cycle,
we haven't paid as much attention to bugs and smaller features as we
have done during previous releases. To address this, we're considering
making Django 1.3 a "feature light" release -- that is, we will spend
more time focussing on little features and long standing bugs, rather
than adding lots of big features like we have done with Django 1.2.
Once 1.2 lands, we'll have some more details about our exact plans for
the 1.3 cycle.
Until then, we'll try to blog every week to give you a status update,
letting you know how many tickets remain, any problems we foresee,
and to provide an updated estimate of the 1.2 final delivery date.
So: there are 120 tickets remaining, but many of these will be bumped
from the final release. It's difficult to know exactly how much work
is left before we do the final ticket cull, but our first-cut revised
estimate for an RC1 release around March 22, with a final release
around March 29. We'll give you another update next week.
As always, any assistance preparing, reviewing or testing patches is
most welcome; the more help we get, the sooner we can release. If you
want to help out,check out the 1.2 todo list [2], find something that
sounds interesting and dig in!
[1] http://code.djangoproject.com/wiki/Version1.2Roadmap
[2]
http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&group=component&milestone=1.2&order=priority
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
