Django 1.2 release schedule - Update 4

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.