Nice, James. Thanks!
On Feb 5, 10:30 pm, James Bennett wrote:
> Tonight we've released Django 1.2 beta 1:
>
> * Blog entry:http://www.djangoproject.com/weblog/2010/feb/06/12-beta-1/
> * Release notes:http://docs.djangoproject.com/en/dev/releases/1.2-beta-1/
&
Tonight we've released Django 1.2 beta 1:
* Blog entry: http://www.djangoproject.com/weblog/2010/feb/06/12-beta-1/
* Release notes: http://docs.djangoproject.com/en/dev/releases/1.2-beta-1/
* Checksums: http://media.djangoproject.com/pgp/Django-1.2-beta-1.checksum.txt
Note that this consti
Hope you feel better today :)
On Feb 5, 3:35 am, James Bennett wrote:
> Due to a combination of exhaustion and illness on the part of the
> release manager (me), I'm going to slide the 1.2 beta release one day;
> that means beta tomorrow (Friday, February 5, probably evening-is
Due to a combination of exhaustion and illness on the part of the
release manager (me), I'm going to slide the 1.2 beta release one day;
that means beta tomorrow (Friday, February 5, probably evening-ish US
Central time). If anyone's got last-minute commits, get 'em in.
--
&qu
On Thu, Feb 4, 2010 at 5:22 AM, Richard Davies
wrote:
> On Feb 2, 9:19 pm, James Bennett wrote:
>> Also, note that this will be the final feature freeze for 1.2;
>> if it ain't in trunk when I roll the tarball, it'll have to wait until 1.3.
>
> Any chance of getting #10476 and #11156 in?
>
> Both
Is starting the deprecation process for something a feature or a bug? If
feature, we should start the process for the psycopg1 backend (discussed
here:
http://groups.google.com/group/django-developers/browse_thread/thread/ac7874cac8ece97)
before Thursday. Near as I can tell it hasn't been marked pe
On Feb 2, 9:19 pm, James Bennett wrote:
> Also, note that this will be the final feature freeze for 1.2;
> if it ain't in trunk when I roll the tarball, it'll have to wait until 1.3.
Any chance of getting #10476 and #11156 in?
Both minor features, but both on the Version1.2Feature wiki page
(und
On Wed, Feb 3, 2010 at 5:19 AM, James Bennett wrote:
> I'm kind of choosing this arbitrarily, but as far as I can tell we
> should be good to go for rolling a beta any time. So I'm picking
> Thursday.
>
> If there are any blockers I'm not aware of, let me know. Also, note
> that this will be the f
I'm kind of choosing this arbitrarily, but as far as I can tell we
should be good to go for rolling a beta any time. So I'm picking
Thursday.
If there are any blockers I'm not aware of, let me know. Also, note
that this will be the final feature freeze for 1.2; if it ain't in
trunk when I roll the
I would also like to point out: http://code.djangoproject.com/ticket/12600
It does break existing code however, because it will look for the
preview template somewhere else.
On Jan 28, 2:25 am, Ben Firshman wrote:
> On 27 Jan 2010, at 22:50, Ben Firshman wrote:
>
>
>
> > On 27 Jan 2010, at 15:36
On 27 Jan 2010, at 22:50, Ben Firshman wrote:
>
> On 27 Jan 2010, at 15:36, Russell Keith-Magee wrote:
>>
>> However, my initial impression: one way to dramatically increase your
>> chances is to make sure the patch applies to trunk, and passes all the
>> tests. Neither of these things are true
On 27 Jan 2010, at 15:36, Russell Keith-Magee wrote:
>
> However, my initial impression: one way to dramatically increase your
> chances is to make sure the patch applies to trunk, and passes all the
> tests. Neither of these things are true at present. Using the most
> recent patch on the ticket
On Wed, Jan 27, 2010 at 9:52 PM, Ben Firshman wrote:
> On 25 Jan 2010, at 18:55, Jacob Kaplan-Moss wrote:
>
> Are we on track for releasing a 1.2 beta this week?
>
> That'd match our original schedule, but we did miss 1.2 alpha by a
> week or so, so perhaps we should push
On 25 Jan 2010, at 18:55, Jacob Kaplan-Moss wrote:
Are we on track for releasing a 1.2 beta this week?
That'd match our original schedule, but we did miss 1.2 alpha by a
week or so, so perhaps we should push back the beta to match? Or is
everyone happy with progress to date and ready to
On Tuesday 26 January 2010 11:30:45 Florian Apolloner wrote:
> Hi,
>
> I am far away from beeing a commiter, but would like to get some
> thoughts about the AnonymousUser permission checks written down
> (I'll keep it short to not hijack this thread): By the time I
> moved permission checks to t
Am 26.01.2010 um 12:30 schrieb Florian Apolloner:
> I am far away from beeing a commiter, but would like to get some
> thoughts about the AnonymousUser permission checks written down (I'll
> keep it short to not hijack this thread): By the time I moved
> permission checks to the backends I didn't
Hi,
I am far away from beeing a commiter, but would like to get some
thoughts about the AnonymousUser permission checks written down (I'll
keep it short to not hijack this thread): By the time I moved
permission checks to the backends I didn't thought much about
anonymous users (I guess that was b
On Tue, Jan 26, 2010 at 9:05 AM, Russell Keith-Magee
wrote:
> On Tue, Jan 26, 2010 at 2:55 AM, Jacob Kaplan-Moss wrote:
>> Hey folks --
>>
>> Are we on track for releasing a 1.2 beta this week?
>>
>> That'd match our original schedule, but we did miss 1.2 a
On Tue, Jan 26, 2010 at 7:09 AM, Luke Plant wrote:
> On Monday 25 January 2010 18:55:34 Jacob Kaplan-Moss wrote:
>> Hey folks --
>>
>> Are we on track for releasing a 1.2 beta this week?
>>
>> That'd match our original schedule, but we did miss 1.2 alpha by
On Tue, Jan 26, 2010 at 2:55 AM, Jacob Kaplan-Moss wrote:
> Hey folks --
>
> Are we on track for releasing a 1.2 beta this week?
>
> That'd match our original schedule, but we did miss 1.2 alpha by a
> week or so, so perhaps we should push back the beta to match? Or i
20 matches
Mail list logo
