Tonight we've released Django 1.0.1, a bugfix release in the 1.0
series containing improvements and fixes since the 1.0 release. This
is a recommended upgrade for anyone currently running Django 1.0.
The blog entry announcing the release is here:
http://www.djangoproject.com/weblog/2008/nov/15/10
On Fri, 2008-11-14 at 08:28 -0800, Jonas Pfeil wrote:
> Just to be clear we are talking about the same thing: With "persistent
> filters" I just mean "going back to the _filtered_ change list after
> editing an item". I don't think it makes sense to make them any more
> persistent :) Clicking on
Hi folks --
We held a set of sprints leading up to 1.0, and I really think those
helped get the release out on time. So let's do it again!
We've got less of a crazy schedule this time around, so I don't think
we need *quite* as many sprints as last time. I'd like to hold at
least one each in Dec
Must have been looking at the 0.96 version, now I can't find it either.
Sorry for the confusion.
Russell Keith-Magee wrote:
> On Thu, Nov 13, 2008 at 12:50 PM, Info Cascade
> <[EMAIL PROTECTED]> wrote:
>
>> The documentation says that implementation of one-to-one relationships
>> will be chang
Just to be clear we are talking about the same thing: With "persistent
filters" I just mean "going back to the _filtered_ change list after
editing an item". I don't think it makes sense to make them any more
persistent :) Clicking on the link to the change list on the admin
home page should give
Hi,
On Fri, Nov 14, 2008 at 6:37 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> Not the *best* place to post this, but it does relate to Django dev.
>
> Is it possible, and if so how, could one branch the Django trunk, and
> throw it on Github?
You should really have your own branch made up of S