1.1.1 remedies a security issue in 1.1 (http://www.djangoproject.com/
weblog/2009/oct/09/security/), so while technically the two versions
are different, there's no reason to run any 1.1 release other than
1.1.1.
As for whether 1.0 (which was patched at the same time to 1.0.4) or
1.1 is better, 1
On 7 Lis, 09:03, Good Z wrote:
>
> Any feedback on 1.1 for production software is appreciated.
>
I recently migrated quite big live service from 1.0.2 to 1.1.1
and I didn't observe even single migration-related problem.
It was probably the smoothest upgrade I had in a few years.
But I remember
sometimes there is this error after upgrade to 1.1.1:
http://groups.google.com/group/django-users/browse_thread/thread/c6a61a3788138745
On Nov 7, 9:29 am, Tomasz Zieliński
wrote:
> On 7 Lis, 09:03, Good Z wrote:
>
>
>
> > Any feedback on 1.1 for production software is appreciated.
>
> I rece
2009/11/10 Evgeny :
> sometimes there is this error after upgrade to 1.1.1:
>
> http://groups.google.com/group/django-users/browse_thread/thread/c6a61a3788138745
>From the sound of it, this was a configuration problem on your system,
and not an issue with Django (any time deleting an older copy o
4 matches
Mail list logo
