Weblog

January archive

Django Sprint in Utrecht, Netherlands

January 31, 2013

I’m very happy to announce that a two-day Django sprint will take place on February 23-24 in Utrecht, Netherlands. This event is organized by the Dutch Django Association. Sign up!

The venue is the Dutch Game Garden in Utrecht. The sprint will start on Saturday, February 23rd at 10:00 CET and and finish on Sunday, February 24 around 22:00 CET.

If this is your first time contributing to Django itself, you should review the contributing guide and set up your clone of the Django git repository.

Hopefully Django 1.5 will be released by then. Even if it isn't, we'll be able to focus on bugfixes and improvements for Django 1.6, as the 1.5 branch was forked from master in October 2012.

Thanks to the Django Software Foundation and to the Dutch Django Association association, three core developers will participate on site: Jannis Leidel, Florian Apolloner, and myself (Aymeric Augustin).

If you’re unable to come to Utrecht, you're welcome to contribute to the sprint online. Sprinters and core developers will be available in the #django-sprint IRC channel on FreeNode.

We hope you can join us and help make the sprint as successful as possible!

DjangoCon US 2014-15 contract awarded to The Open Bastion

January 27, 2013

In November, the Django Software Foundation issued a Request For Proposals for the organisation of DjangoCon US 2014 and 2015.

Today, the Django Software Foundation is proud to announce we have selected The Open Bastion as the winning bidder. The Open Bastion has been responsible for organizing DjangoCon US since 2010, and will be organizing DjangoCon US 2013, to be held in Chicago.

We hope you'll join us in Chicago this year, and join us again in 2014 and 2015 for DjangoCon US.

Delays in the final release of Django 1.5

January 24, 2013

Django 1.5 Release Candidate 1 was released on January 4, and at the time of that release, we were expecting the final release to occur approximately 1 week later.

Unfortunately, testing of the release candidate has revealed several problems. In order to ensure the quality of Django 1.5, we've decided to delay the release.

In order to ensure that we've found all the problems, we're going to wait a week or so, then issue a second release candidate. Assuming no problems are found with this second release candidate, the final release will occur a week later.

We apologize for the delays in releasing 1.5 final. In an ideal world, we'd release on time and with no bugs; however, since that wasn't possible, we've opted to ensure the quality of the release, rather than hit a specific deadline. If you want to help ensure the quality of the final release, grab the code from the 1.5 release branch, and test it against your own projects and test suites.

Django 1.5 release candidate

January 4, 2013

As part of the Django 1.5 release process, today we've released Django 1.5 release candidate 1, a preview/testing package for Django 1.5. As with all pre-release packages, this is not for production use, but if you'd like to try out some of the new goodies coming in 1.5, or if you'd like to pitch in and help us fix bugs before the final 1.5 release, feel free to grab a copy and give it a spin.

In particular, we ask users of this release candidate to watch for and report any major bugs they encounter; if no release-blocking bugs are reported, Django 1.5 will be released in approximately one week.

You can get a copy of the 1.5 release candidate from our downloads page, and we recommend you read the release notes. Also, for the security conscious, signed MD5 and SHA1 checksums of the 1.5 release candidate are available.

Also, please note that Django 1.5 now requires a minimum of Python 2.6; Python 2.5 is no longer supported. Python 3.x releases, starting with Python 3.2, are experimentally supported in this release. For more information on Python 3 support, and the testing Django 1.5 will still need, see this blog post.