在Django中跟踪trunk是否安全？ [英] Is it safe to track trunk in Django?

问题描述

我目前正在为某些个人项目使用 Django 1.1 beta ，并计划开始与中继线混合，以查看新的东西。但是我可能会在专业的基础上开始使用它，而且我需要知道 trunk 是否稳定，足以在生产中使用，或者我应该坚持1.0进行关键任务系统。

I'm currently using Django 1.1 beta for some personal projects, and plan to start messing arround with the trunk to see the new stuff under the hood. But I might start using it on a professional basis, and I'd need to know if trunk is stable enough for using in production, or I should stick to 1.0 for mission critical systems.

将所有信息放在正确的答案中。

Putting all the information in answer for correctness.

推荐答案

首先， Django 1.1 是更接近发布一步， RC1可供下载。

有了这个，我发现了一些有用的东西。

With that out of the way, I've found some useful things.

• 如果你计划跟随这个项目您应该留意 D jango deprecation时间轴，沿着 Django弃用政策。


• 另一个重要的地方是， API稳定性页面的文档。


• 关注 django - 用户邮件列表，以及 django-developer邮件列表

• If you are planning following this project, you should keep an eye in the Django deprecation timeline, along the Django deprecation policy.
• Another important place to look, is the API Stability page of the documentation.
• Keep an eye on the django-users mailing list, as well as the django-developer mailing list.

我还缺少一些我应该看的东西？

Am I missing something I should be looking too?

Django 1.1被发布！您可以立即下载 的！ ：）

Django 1.1 was released!!! You can download it right now! :)

如果不支持 trunk 以下内容，问题仍然存在：Django didn没有，您只有头 trunk ）

The question remains if trunk following is not recommended (once upon a time, Django didn't have releases, you only had head of trunk)

根据 Theionion ，已从Drupal迁移到Django ， Django trunk非常稳定。

这篇关于在Django中跟踪trunk是否安全？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！