- Recent
- Popular
- Tags (1)
- Subscribers (20)
- Django 1.0.2 releasedNovember 19
-
Shortly after last week's Django 1.0.1 release, several people noted that the packaging script used to produce the release omitted several directories from the Django source tree; mostly this affected some unit tests, but at least one of the omitted directories affected the use of Django itself (specifically, of django.contrib.gis). So tonight we're issuing Django 1.0.2, which is built around an updated packaging script and should resolve these problems.
This is a recommended upgrade for anyone using or targeting Django 1.0 or Django 1.0.1; to obtain a copy, swing by the downloads page, and don't forget to read the release notes. For the security conscious, a signed file containing the package's checksums is, as always, available.
- Django 1.0.1 released!November 15
-
Following the previously-announced schedule, today the Django team has released Django 1.0.1. This is a bugfix-only release containing fixes and improvements to the Django 1.0 codebase, and is a recommended upgrade for anyone using or targeting Django 1.0.
For full details, check out the 1.0.1 release notes, and to grab a copy of Django 1.0.1, visit the downloads page. For the security-conscious, a file containing checksums of the 1.0.1 package, signed with the release manager's key, is available.
And with Thanksgiving coming up in the US, your friendly local release manager would like to pause for a moment and express thanks, on behalf of myself and the Django development team, for all the work put in by all the members of our community to help keep the releases coming, the tickets triaged and the bugs fixed. We wouldn't be able to do it without all of you, so give yourselves a big pat on the back and see if you can't sneak an extra slice of pie come Thanksgiving dinner.
We'll see you again in a few months, for either Django 1.0.2 or Django 1.1. Happy holidays!
- Django 1.0.1 beta availableOctober 31
-
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)
- Upcoming Django releasesOctober 24
-
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
- Django 1.0 released!September 3
-
No, you’re not hallucinating, it’s really here.
Around three years ago, Adrian, Simon, Wilson and I released some code to the world. Our plan was to hack quietly on it for a bit, release a solid 1.0 release, and then really get the ball rolling.
Well.
What happened, of course, was that an amazing community sprung up literally overnight — our IRC channel had over a hundred people in it the day after release, and it’s never been that “empty” since.
I really can’t stress enough how amazing our community of users and developers are. About half of the code that’s gone into Django over the past three years has been contributed by someone other than a core committer. Since our last stable release, we’ve made over 4,000 code commits, fixed more than 2,000 bugs, and edited, added, or removed around 350,000 lines of code. We’ve also added 40,000 lines of new documentation, and greatly improved what was already there.
Django 1.0 represents a the largest milestone in Django’s development to date: a web framework that a group of perfectionists can truly be proud of. Without this amazing community, though, it would have never happened.
You can download Django 1.0 on the Django downloads page, and read the complete release notes.
For distributors and for verification purposes, a file containing
