2014-09-03 10:40 GMT+02:00 Tom Evans <[email protected]>: > > I think it was more distraction by topics he had not come across. We > set him off by saying "look at the release notes, go thru each change > in turn, see if we are affected and what we need to fix it". >
Thanks Tom for the details. I understand better. Upgrading Django exposes you to components or features you didn't even know existed. The time I spent triaging Trac tickets gives me a massive advantage there :-) The problem then was that he was new. He hadn't had to deal too much > with TZ support, so adding TZ support to our project meant a day of > learning about how TZ work in UNIX. > You went for USE_TZ = True. That required a lost of work to adjust your entire codebase. I'm considering that a new feature for your project. If you wanted to upgrade as fast as possible, you could have kept the legacy behavior with USE_TZ = False. That was the default for projects upgraded from 1.3. Similarly, changing the project layout is a good thing, but then he > spent a day learning about package layouts - not a bad thing by any > means, but in the 1.3 -> 1.4 release there are 75 similarly complex > enhancements/deprecations/incompatibilities - it just takes some time > to go through if you have not come across that topic before, eg, > clickjacking. Right, this was another complicated change you couldn't skip. 1.5 and 1.6 must have been easier than 1.4. 1.7 may be more difficult because of migrations and app-loading. If anyone has improvements to suggest for the documentation, please do! -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mU23ag9N4vnuajfFsOdtYKBp1RttE3WqG%2B36BUXo6yQ4g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
