我应该从 Django 1.2.5 迁移到 1.3.x 吗？是否存在未记录的问题？
简短问题
是否有任何令人信服的理由将 Django 1.2.5 更新到 1.3？如果发行说明中提到的更改不会直接影响我的应用程序。
编辑：
为了更好地澄清我的问题（感谢 S.Lott！）：如果从版本 1.2.5 升级，Django 1.3 的发行说明中是否有任何我应该注意的问题未提及？
背景
我在 1.2.5 上完成了所有开发，没有遇到任何问题。我将在接下来的一两周内部署我的应用程序，它的生命周期将是 18 - 24 个月的持续使用。
次要（更一般的问题）
在发布之前，获取依赖项的最新和最好（稳定）版本是一个好习惯吗？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
你需要理由吗？只需查看发行说明即可。他们很好地概述了新功能和向后不兼容的更改。我很高兴将我的所有 Django 项目迁移到 1.3，我特别高兴的是静态文件管理方式的变化。基于类的视图非常好，改进的日志记录支持也很棒。如果你有时间就去吧。迁移不需要太多的工作。一般来说，我会尽可能保持最新状态。
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.
迁移到 Django 的新版本（尤其是从之前的版本）非常简单，一个项目只需不到十分钟（如果不是超级复杂的话）。
如果它运行了 18 到 24 个月，我最好升级。在 Django 发布一两个版本之后（每年一个主要版本），它们将不再支持旧版本的安全更新。为了节省时间，您可以升级到 1.3，然后不需要进一步升级，除非您的项目运行时间更长。
Migrating to a new version of Django (especially from a directly previous release) is really easy and takes less than ten minutes for one project (if its not super complex).
It it's running for 18 to 24 months I would better upgrade. After one or two more releases of Django (one major release each year) they will simply not support security updates for older versions anymore. To be be save you can make the step to 1.3 and then don't need to upgrade further, except your project is running even longer.
正如我曾经在某处读到的那样，Django 发布主要是因为人们询问发布。除此之外，坚持主干版本是完全可以的。
As I once read somewhere, Django has releases mostly because people ask about releases. Other than that, it's perfectly ok to stick to the trunk revision.