upgrading django applications to recent revisions
With the release of django 1.0 taking place in less than one month, there've been a lot of movement in django's svn repositories. Both alpha and alpha 2 versions were released last weeks and, as we could read in empty thoughts (the weblog from Michael Trier), there has been some new improvements/changes that will result in our webapps/websites crashing.
Of course, as everything else in django, the changes are well documented, and there is even a BackwardsIncompatibleChanges page in the project wiki, where you can get more information about the changes and how to solve the posible problems derivated from them.
I've suffered such incompatible changes myself during the first codigo23 sprint last week. Nothing really difficult to solve (mostly the move from admin to newforms-admin). Even some hours ago, I've found that our code have problems with the latest alpha 2 release (things related to the FileStorage refactoring).
If you are planning to upgrade your django-based webapps/websites to the latest revision, perhaps you will find useful a post from Ross Poulton in his blog. With "How I Moved My Commercial Projects to Newforms-Admin", Ross explains how he upgraded some well-known sites like djangosites.com in an easy way.