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.
我目前正在使用Django 1.1 beta进行一些个人项目,并计划开始使用后备箱来查看新内容。但是我可能会在专业的基础上开始使用它,而且我需要知道主干是否足够稳定以便在生产中使用,或者我应该坚持1.0用于关键任务系统。
Edit
Putting all the information in answer for correctness.
将所有信息都放在正确的答案中。
5 个解决方案
#1
You probably shouldn't pull Django trunk every day, sometimes there are big commits that might break some things on your site. Also it depends what features you use, the new ones will of cause be a bit more buggy than older features. But all in all there shouldn't be a problem using trunk for production. You just need to be careful when updating to latest revision.
你可能不应该每天都拉Django主干,有时会有大的提交可能会破坏你网站上的一些东西。此外,它取决于您使用的功能,新功能将比旧功能更多。但总而言之,使用主干进行生产应该不会有问题。更新到最新版本时,您需要小心。
You could for example set up a new virtual environment to test, before updating the live site. There are many ways to do something simelar, but I will let you take your pick.
例如,您可以在更新实时站点之前设置要测试的新虚拟环境。有许多方法可以做一些simelar,但我会让你接受你的选择。
#2
I think you've done a good job of gathering the right links in the question. The only links I would add are:
我认为你在收集问题中的正确链接方面做得很好。我要添加的唯一链接是:
- http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
- http://code.djangoproject.com/wiki/FutureBackwardsIncompatibleChanges
The first is for anyone still on a pre 1.0 release and wondering about the upgrade path, even to the trunk. The second is a work in progress it seems, and may be updated as things progress toward the 2.0 release.
第一个是针对仍然处于1.0版本之前的人,并且想知道升级路径,甚至是后备箱。第二个是正在进行的工作,并且可能会随着2.0版本的发展而更新。
#3
As with the trunk of any software project, it's only as stable as the people commiting things test for. Typically this is probably pretty stable, but you need to be aware that if you get caught with a 'bad' version (which can happen), your site/s just might come down over it temporarily.
与任何软件项目的主干一样,它只能像人们进行测试一样稳定。通常情况下,这可能非常稳定,但您需要注意,如果您遇到“糟糕”版本(可能会发生),您的网站可能会暂时失效。
#4
For what it's worth, I've read in multiple places (in the documentation here: http://www.djangoproject.com/download/ (see the side bar) and from the project's lead developers in a book of theirs) that it's fine to use the trunk. Many of their own developers use trunk for their sites and so they have incentive to keep it stable.
对于它的价值,我已经在多个地方阅读了(在这里的文档中:http://www.djangoproject.com/download/(参见侧栏)和项目的主要开发人员在他们的书中)它是很好用的行李箱。他们的许多开发人员都在他们的网站上使用trunk,因此他们有动力保持稳定。
Recently, however, they mentioned that the 1.1 RC along with any other pre-release packages should not be used for production ( http://www.djangoproject.com/weblog/2009/jul/21/rc/ ) so the signals are somewhat mixed.
然而,最近他们提到1.1 RC和任何其他预发布包不应该用于生产(http://www.djangoproject.com/weblog/2009/jul/21/rc/)所以信号是有些混乱。
That said, my personal feeling is that the trunk is very stable most of the time but as with any code you haven't used before you should run it through its paces before deploying anything.
也就是说,我个人的感觉是,主干在大多数时间都非常稳定,但是在使用任何代码之前,你应该在部署任何代码之前运行它。
As the other posters said though: the choice is ultimately yours to make based on your best judgement.
正如其他海报所说的那样:根据你的最佳判断,你最终会做出选择。
#5
First, Django 1.1 is one step closer to being released, as RC1 is available for download.
首先,由于RC1可供下载,因此Django 1.1距离发布还有一步之遥。
With that out of the way, I've found some useful things.
有了这个,我发现了一些有用的东西。
- 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.
如果您计划关注此项目,您应该关注Django弃用政策中的Django弃用时间表。
另一个重要的地方是文档的API Stability页面。
请关注django-users邮件列表以及django-developer邮件列表。
Am I missing something I should be looking too?
我错过了一些我应该看的东西吗?
Edit
Django 1.1 was released!!! You can download it right now! :)
Django 1.1发布了!你现在可以下载它! :)
The question remains if trunk following is not recommended (once upon a time, Django didn't have releases, you only had head of trunk)
问题仍然是如果不推荐躯干跟踪(曾几何时,Django没有释放,你只有主干头)
Acording to the tech team at The Onion, which has migrated from Drupal to Django, Django trunk is extremely stable.
根据Onion的技术团队,从Drupal迁移到Django,Django主干非常稳定。
#1
You probably shouldn't pull Django trunk every day, sometimes there are big commits that might break some things on your site. Also it depends what features you use, the new ones will of cause be a bit more buggy than older features. But all in all there shouldn't be a problem using trunk for production. You just need to be careful when updating to latest revision.
你可能不应该每天都拉Django主干,有时会有大的提交可能会破坏你网站上的一些东西。此外,它取决于您使用的功能,新功能将比旧功能更多。但总而言之,使用主干进行生产应该不会有问题。更新到最新版本时,您需要小心。
You could for example set up a new virtual environment to test, before updating the live site. There are many ways to do something simelar, but I will let you take your pick.
例如,您可以在更新实时站点之前设置要测试的新虚拟环境。有许多方法可以做一些simelar,但我会让你接受你的选择。
#2
I think you've done a good job of gathering the right links in the question. The only links I would add are:
我认为你在收集问题中的正确链接方面做得很好。我要添加的唯一链接是:
- http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
- http://code.djangoproject.com/wiki/FutureBackwardsIncompatibleChanges
The first is for anyone still on a pre 1.0 release and wondering about the upgrade path, even to the trunk. The second is a work in progress it seems, and may be updated as things progress toward the 2.0 release.
第一个是针对仍然处于1.0版本之前的人,并且想知道升级路径,甚至是后备箱。第二个是正在进行的工作,并且可能会随着2.0版本的发展而更新。
#3
As with the trunk of any software project, it's only as stable as the people commiting things test for. Typically this is probably pretty stable, but you need to be aware that if you get caught with a 'bad' version (which can happen), your site/s just might come down over it temporarily.
与任何软件项目的主干一样,它只能像人们进行测试一样稳定。通常情况下,这可能非常稳定,但您需要注意,如果您遇到“糟糕”版本(可能会发生),您的网站可能会暂时失效。
#4
For what it's worth, I've read in multiple places (in the documentation here: http://www.djangoproject.com/download/ (see the side bar) and from the project's lead developers in a book of theirs) that it's fine to use the trunk. Many of their own developers use trunk for their sites and so they have incentive to keep it stable.
对于它的价值,我已经在多个地方阅读了(在这里的文档中:http://www.djangoproject.com/download/(参见侧栏)和项目的主要开发人员在他们的书中)它是很好用的行李箱。他们的许多开发人员都在他们的网站上使用trunk,因此他们有动力保持稳定。
Recently, however, they mentioned that the 1.1 RC along with any other pre-release packages should not be used for production ( http://www.djangoproject.com/weblog/2009/jul/21/rc/ ) so the signals are somewhat mixed.
然而,最近他们提到1.1 RC和任何其他预发布包不应该用于生产(http://www.djangoproject.com/weblog/2009/jul/21/rc/)所以信号是有些混乱。
That said, my personal feeling is that the trunk is very stable most of the time but as with any code you haven't used before you should run it through its paces before deploying anything.
也就是说,我个人的感觉是,主干在大多数时间都非常稳定,但是在使用任何代码之前,你应该在部署任何代码之前运行它。
As the other posters said though: the choice is ultimately yours to make based on your best judgement.
正如其他海报所说的那样:根据你的最佳判断,你最终会做出选择。
#5
First, Django 1.1 is one step closer to being released, as RC1 is available for download.
首先,由于RC1可供下载,因此Django 1.1距离发布还有一步之遥。
With that out of the way, I've found some useful things.
有了这个,我发现了一些有用的东西。
- 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.
如果您计划关注此项目,您应该关注Django弃用政策中的Django弃用时间表。
另一个重要的地方是文档的API Stability页面。
请关注django-users邮件列表以及django-developer邮件列表。
Am I missing something I should be looking too?
我错过了一些我应该看的东西吗?
Edit
Django 1.1 was released!!! You can download it right now! :)
Django 1.1发布了!你现在可以下载它! :)
The question remains if trunk following is not recommended (once upon a time, Django didn't have releases, you only had head of trunk)
问题仍然是如果不推荐躯干跟踪(曾几何时,Django没有释放,你只有主干头)
Acording to the tech team at The Onion, which has migrated from Drupal to Django, Django trunk is extremely stable.
根据Onion的技术团队,从Drupal迁移到Django,Django主干非常稳定。