On Monday, 6 August 2012 15:29:04 UTC+10, DrMeers wrote:
>
> Monday 20th August 0900-2359 AEST at PyCon Australia 2012 (Hobart) [1]
>
> The Interaction Consortium [2] have kindly offered to provide pizza
> and beer (presumably only for those physically present ;)
>
> Join us via the
Monday 20th August 0900-2359 AEST at PyCon Australia 2012 (Hobart) [1]
The Interaction Consortium [2] have kindly offered to provide pizza
and beer (presumably only for those physically present ;)
Join us via the #django-sprint IRC channel on Freenode; see [3] for
more information.
[1]
Ivan Sagalaev wrote:
> I still care very much for Postgres thread-safety ticket (#900). Seeing
> that Eugene will cover MySQL patches I wonder if it's Postgres cousin is
> on the list too?
Yes. I'll try to cover all related tickets.
Thanks,
Eugene
Jacob Kaplan-Moss wrote:
>You can find those topics and notes from our meeting today
>at http://code.djangoproject.com/wiki/PyConSprint06.
>
>
What counts as "crash-level bugs" and "outstanding patches"?
I still care very much for Postgres thread-safety ticket (#900). Seeing
that Eugene will
On Mon, 2006-02-27 at 02:15 -0600, Jeremy Dunck wrote:
> On 2/27/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> ...
> > On other Open Source projects I've worked on, there has been a way to
> > indicate in the bug tracking system that a patch was attached to a
> > report. Either by adding
On 2/27/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
...
> On other Open Source projects I've worked on, there has been a way to
> indicate in the bug tracking system that a patch was attached to a
> report. Either by adding [patch] to the title or setting a "patch"
> keyword or something
