Weblog

March archive

Django 1.2 release schedule - Update 2

March 23, 2010

This week has seen more good progress towards the 1.2 release milestone. We are now down to 69 open tickets, of which 23 are documentation or translation updates that can be addressed after the release candidate lands. This leaves 46 substantive tickets before we have a release candidate.

To help squash this bug list, there is another development sprint planned for this weekend. If you can spare a few hours to help kill some release blocking bugs, why not join in! Add your name to the list of sprinters on the wiki, and join us online on IRC in #django-sprint.

There's no change to the estimated release dates this week. We're still aiming at a RC1 release around April 5, with a final release around April 12.

As always -- any and all assistance is most welcome; the more assistance we get, the faster 1.2 will land.

Django 1.2 release schedule - Update 1

March 16, 2010

At the time of our last blog post, there were 120 tickets open. Over the last week, we have purged a bunch of tickets that weren't critical to the release of 1.2, and we have made 50 Subversion commits. There have also been a couple of new tickets added.

As a result of this activity, 84 tickets remain. Of those tickets, 21 are documentation and translation updates. This leaves 63 substantive tickets that need to be addressed before we have a release candidate.

There are three areas in particular that have large ticket counts. Not surprisingly, these areas correspond to the three areas of biggest change in 1.2:

  1. Regressions in query behavior caused by the multi-db refactoring,
  2. Changes in admin behavior caused by the admin javascript improvements, and
  3. Edge cases in localization handling.

Many of these issues are small oversights or minor corrections. However, there are a couple of tickets (for example #13023) that aren't trivial, and will require some significant design work.

As a result, we're going to push back the expected release date by another 2 weeks. This would put an RC1 release around April 5, with a final release around April 12.

To help speed things along, we'll be running a development sprint focused solely on tickets for 1.2; if you'd like to join in, add your name to the list of sprinters on the wiki. We're aiming to sprint either this weekend (March 20/21) or next (March 27/28), depending on which weekend has the best availability for the folks who sign up.

As always -- any and all assistance is most welcome; the more assistance we get, the faster 1.2 will land.

Django 1.2 release schedule

March 9, 2010

Those of you that have been paying attention to the Django release roadmap 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's release cycle is generally date-based, we also try to keep our release dates flexible to account for bugfixing time. At the beginning of the development sprints at PyCon a few weeks ago, over 300 tickets were still open on the Django 1.2 milestone. Now it's down to 120 (we've been clearing out, on average, about ten tickets a day), but that's still a lot more than we're comfortable shipping; as a result, we're pushing back the final 1.2 release a bit.

Some of the tickets still open for 1.2 are documentation or translation updates; these will be dealt with before the final 1.2 release. Others are minor bugs or edge cases which are difficult to trigger or unlikely to cause serious problems in actual deployment; these tickets will likely be bumped to a pure-bugfix release in the 1.2 series, or to 1.3 as warranted.

Over the next couple of days, the Django core team will be reviewing all of the currently-open tickets, and identifying those which:

  • reveal a significant flaw in a feature added during the 1.2 cycle, or
  • have the potential to cause data loss or other serious consequences in actual deployment.
  • Tickets which don't meet these criteria may be removed from the 1.2 milestone, or may simply be left out of the final release. We won't forget about these issues -- they'll still be in Trac, and they will be addressed -- but bugfix work prior to the 1.2 release will focus in major issues fitting the criteria above.

    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 be posting here every few days 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 quite a few of these 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 is for an RC1 release around March 22, with a final release around March 29. This is, for those of you who were following along during the early parts of the 1.2 cycle, roughly consistent with extra time added to the release schedule for the 1.2 alpha and beta milestones.

    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, find something that sounds interesting and dig in!