Feel free to test queryset-refactor branch - Django users

Message from discussion Feel free to test queryset-refactor branch
MIME-Version: 1.0
Message-ID: <aab90eac-8334-4ccd-9eee-d4006f666f9f@u36g2000prf.googlegroups.com>
Date: Sun, 13 Apr 2008 04:51:52 -0700 (PDT)
In-Reply-To: <1208085814.17060.31.camel@counterweight.tredinnick.org>
References: <1208085814.17060.31.camel@counterweight.tredinnick.org>
User-Agent: G2/1.0
Subject: Re: Feel free to test queryset-refactor branch
From: Julien <jpha...@gmail.com>
To: Django users <django-users@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Malcolm,

I've been using the branch on a project in development for a few weeks
now, and haven't come across any issue yet - although I can't say I've
pushed it to its limits.

Glad to hear it's close to be merged to trunk.

Thanks so much for this massive contribution!

Best,

Julien

On Apr 13, 9:23 pm, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> We're getting pretty close to merging queryset-refactor into trunk and
> would like to do this as soon as practical. There are still a couple of
> enhancements to add (#5420, mostly), one bug to fix (#5937) and some
> internal tweaking to do, but all the main stuff is ready to be used.
>
> So if anybody wants to test it out, go ahead. Read the wiki page[1] if
> you've got code that does any slightly unusual stuff, but for existing
> code that works on trunk, there shouldn't be any real changes required.
>
> [1]http://code.djangoproject.com/wiki/QuerysetRefactorBranch
>
> File any bug reports in Trac against the queryset-refactor
> "version" (please do NOT put the qs-rf keyword on the ticket; I'm using
> that for other purposes). Bug reports that are regressions from existing
> functionality are more interesting and important at the moment than
> feature enhancements to the new features, since the latter case can be
> dealt with at our leisure (they're not features that people are already
> relying upon).
>
> If you see any different results testing against the branch compared to
> trunk, it would be interesting to know about them. Reduce it to a small
> example before opening a ticket, wherever possible. Please don't make me
> wade through dozens of lines of code just to get to one query that is
> relevant. Bear in mind, though, that the difference could be because a
> bug existed in trunk and the branch is now giving the correct result. So
> make sure your test case is valid (even I got bitten by that in a
> project I wrote).
>
> Regards,
> Malcolm
>
> --