Someone using django trunk for production?
I need to use aggregation features of django 1.1 (i need AVG, SUM). My production site uses 1.0.2. Can I upgrade to trunk without worrying? -- Alessandro Ronchi Skype: aronchi http://www.alessandroronchi.net SOASI Soc.Coop. - www.soasi.com Sviluppo Software e Sistemi Open Source Sede: Via Poggiali 2/bis, 47100 Forlì (FC) Tel.: +39 0543 798985 - Fax: +39 0543 579928 Rispetta l'ambiente: se non ti è necessario, non stampare questa mail --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Someone using django trunk for production?
Alessandro Ronchi wrote: > I need to use aggregation features of django 1.1 (i need AVG, SUM). > > My production site uses 1.0.2. > > Can I upgrade to trunk without worrying? > > Are you using the width_field and height_field properties of ImageField at all? They're broken if used in the admin module after revision 9765. That's the only issue I'm aware of with trunk. Regards, Andrew Ingram --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Someone using django trunk for production?
On Sat, Jan 31, 2009 at 7:24 PM, Alessandro Ronchi wrote: > > I need to use aggregation features of django 1.1 (i need AVG, SUM). > > My production site uses 1.0.2. > > Can I upgrade to trunk without worrying? Would I expect to see any major failures? No. Would I keep my eyes open just in case? Yes. We try fairly hard to keep trunk stable, and there haven't been any backwards incompatible changes to public API, so I wouldn't expect to see any major problems in switching from v1.0.2 to trunk SVN. However, there will occasionally be bugs in trunk (such as the file field problem Andrew mentioned). If you intend to move to trunk, you need to plan on testing a little more thoroughly than you would need to under v1.0.2, and sometimes you may need to patch your local trunk checkout to overcome bugs that have not yet been fixed. The extent to which these bugs affect you will depend entirely upon your own codebase. You will need to balance your willingness to deal with these problems against your desire to use the new aggregate features. Ultimately, you are the only person that can make that call. Yours, Russ Magee %-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
