Weblog

April archive

Django 1.2 release schedule - Update 7

April 28, 2010

We're in the final stretch As a result of some good bug killing activity over the week, there are just 2 bugs blocking a release candidate. Both of these bugs (#13166 and #13315) are reasonably well understood; they're just waiting on the time needed to polish and commit the patches.

So -- that means we're on target for a release candidate around May 3, with a final release around May 10. The exact date might be off by a day or two, depending on the ability of our esteemed Release Manager James Bennett to find the time to turn the crank and make the official tarballs.

Once we have a release candidate, work will shift to closing the 48 outstanding documentation and translation issues. Luckily, progress on these tickets is much easier than fixing code problems, and there's lots of opportunity to contribute. To that end, we'll be having a virtual sprint on May 8th to try and get as much documentation work sorted out as possible. If you want to help out, join us on #django-sprint on IRC on the 8th; or if you can spare time before then, pick a documentation ticket and work up a patch (or edit a patch on an existing documentation ticket). As always, any and all help is most welcome.

Django 1.2 release schedule - Update 6

April 22, 2010

As with last week, there has been a lot of activity on Django, but this isn't reflected in the overall ticket count. We now have 51 open tickets. However, the good news is that only 8 of these are substantive tickets blocking a release candidate.

Of these final 8 tickets:

  • #12286 doesn't have a test case that can be used to reproduce the problem. Unless someone can provide a test case to reproduce this problem, we will be forced to bump this ticket from the blocking list.
  • #13362 is a test case failure that only affects Python 2.3, and appears to be a problem with the test case, rather than the underlying code.
  • #13339 a problem caused by limitations in Python's strptime() implementation. Unfortunately, there isn't an easy workaround for the problem that doesn't involve duplicating (and fixing) strptime(), and strptime() is a big beast. Unless someone can suggest a brilliant idea, we'll probably have to call this ticket a known limitation, and bump it to a later release.

The remaining 5 tickets all have reasonable known solutions (and working draft patches) - they just require time to apply the fixes.

Although it's entirely possible that we might still make the April 26 deadline, in order to manage expectations, we're going to push the RC date by one more week. Hopefully, this will be the last time we need to extend the deadline. This means we are now targeting a release candidate around May 3, with a final release around May 10.

As always, any and all assistance is most welcome -- especially if you can shed any light on the three problem tickets.

Django 1.2 release schedule - Update 5

April 14, 2010

There has been a lot of activity on Django's trunk this week, but this isn't reflected in the ticket count. The overall open ticket count has increased to 49; this count contains an extra 3 documentation/translation tickets, for a total of 35. This means there are 14 substantive tickets blocking a release candidate -- which is the same as last week.

Although the number of substantive tickets is the same as last week, there has been progress. Several tickets were closed during the week, but an equal number were opened or re-opened as a result of additional testing. The new issues that have been reported are mostly edge cases that were missed by earlier fixes, such as the special handling required to allow for loading code from eggs.

On a positive note, the serious performance regression reported last week has been fixed. The {% url %} template tag has been modified to avoid backtracking problems during template parsing.

As a result of the new tickets, it's unlikely that we will fix all the RC-blocking bugs by April 19. Therefore, we're going to push back the RC date by another week. This means we are now targeting a release candidate around April 26, with a final release around May 3.

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 4

April 7, 2010

We're getting close now! We're down to 46 open tickets, of which 32 are documentation or translation updates. This leaves 14 substantive tickets before we can have a release candidate.

The good news for the week is that we are now at Zarro Boogs for the ORM component. That means there are no known ORM issues blocking a release. The bugs that remain are evenly spread between admin, forms, templating, and internationalization.

The bad news is that there has been one serious regression. Revision 12889 fixed ticket #12945, but in the process introduced a backtracking regular expression that significantly slows down the parsing of {% url %} template tags in certain circumstances. This problem has been logged as ticket #13275, and will be fixed before we make a release candidate.

In light of the otherwise good progress this week, we are not changing the expected release date. This means we are still targeting a release candidate around April 19, with a final release around April 26.

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 3

April 1, 2010

Another good week of progress towards the 1.2 release milestone. We are now down to 54 open tickets, of which 28 are documentation or translation updates that can be addressed after the release candidate lands. This leaves 26 substantive tickets before we have a release candidate.

Although we've been reducing the ticket count by 20-30 tickets per week, some of the progress this week was due to a purge of tickets that were not critical to the 1.2 release. This means we have really had a slight slowdown in progress over the last week. This isn't entirely surprising; as we get closer to the release candidate, the complexity of the tickets that remain tends to increase, as the difficult tickets usually get left until last.

When this slowdown is combined with the fact that this weekend covers the Easter break, it's unlikely we're going to squash all 25 RC-blocking bugs by April 5. Therefore, we're going to push back the RC date by another 2 weeks. This means we are now targeting a release candidate around April 19, with a final release around April 26.

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