Weblog

October archive

Django 1.0.1 beta available

October 31, 2008

Following the previously-announced schedule, today the Django team has released Django 1.0.1 beta 1; this is a preview of the upcoming Django 1.0.1 release, which consists solely of bugfixes and other improvements to the Django 1.0 codebase. This package also follows our policy of maintaining compatibility in the 1.0 release series.

Though it's labeled a "beta", this package is considered to be of production quality; we're releasing it as a preview of Django 1.0.1, and the primary goal of this package is to give users of Django 1.0 an idea of what's been fixed in the codebase since the 1.0 release. If there's a particular issue you're interested in which doesn't seem to be resolved in Django 1.0.1 beta, please consider helping the Django team to fix it by working to develop a patch (see the contribution guidelines for details); Django 1.0.1 is currently scheduled for release on November 14, 2008, which provides a roughly two-week window for submitting patches (and please keep in mind that patches intended for inclusion in 1.0.1 should be against the 1.0.X branch and not trunk).

As such, this release is mostly of interest to developers who want to help out with the Django development process; the final Django 1.0.1 release next month, however, will be a recommended upgrade for all users of Django 1.0.

Also, this beta release does not contain release notes, as there are no new features, only bugfixes. When the final Django 1.0.1 release is issued next month, a list of resolved issues since 1.0 will be included in lieu of release notes.

For verification purposes, a file containing the MD5 and SHA1 checksums of the 1.0.1 beta package has been placed on the djangoproject.com server. The file is PGP-signed with the Django release manager's key; this key has the ID 0x8C8B2AE1 and can be obtained from, e.g., the MIT PGP keyserver.

Upcoming Django releases

October 24, 2008

With Django 1.0 out the door and a successful inaugural DjangoCon behind us, it's time to look ahead to the future, which includes two releases:

  • Django 1.1, currently targeted for release in March 2009.
  • Django 1.0.1, currently targeted for release next month.

Both of these releases, of course, will follow our policy of maintaining compatibility in the 1.0 release series.

Django 1.1 timeline

At the moment, we're aiming to release Django 1.1 on or around March 16, 2009, or roughly six months following the release of Django 1.0. As covered in our release process documentation, the 1.1 release cycle will consist of three phases: feature proposal, feature work and bugfixing/polishing. Since Django 1.1 is happening on a six-month schedule, that means two months for each phase of development; the relevant dates for 1.1 have already been discussed on the django-developers mailing list, but here's the quick breakdown (these dates are still rough estimates, and may change as needed):

  • November 10, 2008: A draft feature list for 1.1 will be posted.
  • November 15, 2008: The 1.1 feature list will be finalized, and no new feature proposals will be accepted for 1.1.
  • January 15, 2009: All major features must be merged into Django trunk, trunk will go into the initial 1.1 feature freeze and work will shift to bugfixes.
  • March 16, 2009: Django 1.1 will be released. As with 1.0, Django 1.1 will be preceded by several pre-release packages to help focus development effort and isolate bugs.

March is still quite a ways off, of course, but keep in mind that the feature-proposal window will be closing in a couple of weeks; if there's something you'd really like to see in Django 1.1 and you haven't already started a discussion of it on the django-developers list, you'll want to do so quickly.

Django 1.0.1 timeline

In the much more immediate future, we're preparing to release Django 1.0.1, which will consist solely of bugfixes and similar improvements to the Django 1.0 codebase. Django 1.0.1 will be a recommended upgrade for anyone who's currently using or migrating to Django 1.0.

Because 1.0.1 will only involve bugfixes, with no feature additions to propose or test, the release process for it will be somewhat abbreviated. Here are the key dates:

  • October 31, 2008: Django 1.0.1 beta. Though it will be called a "beta" release, this will mainly serve as a preview of 1.0.1, and will be production-quality; its primary purpose will be to give folks an idea of what's been fixed since the 1.0 release and a last opportunity to submit patches for any fixes they'd like to see make into into 1.0.1 final.
  • November 14, 2008: Django 1.0.1 will be released.

From an administrative perspective, the 1.0.1 release will not involve any special categorization or milestones in the ticket tracker; with a release of this type, administrivia in Trac is far less important than simple working code, and any bug is a candidate for fixing up until the day of the release. So if there's a particular issue you'd like to see solved for 1.0.1, the best way to ensure the fix makes it into the release is to provide a working patch. As always, preferential treatment will be given to patches which match our contribution guidelines, especially to patches which include unit tests that both demonstrate the bug and demonstrate the success of the solution. Also, remember that patches for 1.0.1 should be created against the 1.0.X release branch, rather than against trunk.