\o/
On Wed, Feb 25, 2015 at 1:08 AM, Tim Graham wrote:
> Zero blockers as of this writing. If we survive the next 12 hours with no
> new ones, I'll release the beta around then (famous last words).
>
>
> On Monday, February 23, 2015 at 7:29:09 PM UTC-5, Tim Graham wrote:
>>
>> Previous two issue
facepalm... Just read that on the contributing guidelines, didn't know that
won't fix bugs where never reopened. So I closed it as won't fix. If the
conversation keeps going I suppose a new bug will be opened.
On Tue, Feb 3, 2015 at 8:56 AM, James Bennett wrote:
> Please keep discussion going in
Hi Jon,
I've reopened the bug so we have a new discussion. I think the things have
changed slightly in the last two years.
Thanks,
Raul
On Tue, Feb 3, 2015 at 2:29 AM, Karen Tracey wrote:
> This has bee brought up before, see:
> https://code.djangoproject.com/ticket/16870
>
> I am not aware of
the first error just tell you:
Try using django.db.backends.XXX, where XXX is one of:
'mysql', 'oracle', 'postgresql', 'postgresql_psycopg2', 'sqlite3'
(not dummy)
Just because users (new ones) can expect that the dummy backend is a correct
one. And as I've
