Should I migrate from Django 1.2.5 to 1.3.x ? Are there any undocumented issues?

Question

Short Question
Are there any compelling reasons to update Django 1.2.5 to 1.3? If the noted changes in the release notes do not impact my application directly.

EDIT:
To better clarify my question (thanks S.Lott!): Are there any issues not mentioned in the Django 1.3's release notes that I should be aware of if upgrading from version 1.2.5?

Background
I have done all of my development on 1.2.5 with no troubles. I will be deploying my application within the next week or two and it's life cycle will be 18 - 24 months of constant use.

Secondary (more general question)
Just prior to a release, is it good practice to get the latest and greatest (stable) version of your dependencies?

Answer 1

You need reasons? Just look at the release notes. They do a very good job outlining both new features and backwards incompatible changes. I have been happy to migrate all of my Django projects to 1.3, I'm particularly happier about the changes to the way static files are managed. Class-based views are quite nice, the improved logging support is great. If you have the time go for it. It shouldn't take too much work to migrate. Generally I stay as current as I can.