安全使用cakephp 3.0生产？ [英] Safe to use cakephp 3.0 for production?

问题描述

我们正在开始一个新项目，它不会在2-3个月内完成。我应该建立在3.0版本上，因为beta 3刚刚发布或者继续使用2.5，并且转换结束3.0稳定终于出来了？

We are starting a new project and it won't be done for 2-3 months. Should I build on version 3.0 since beta 3 was just released or continue with 2.5 and convert over when 3.0 stable is finally out?

推荐答案

您需要定义安全对您的标准的意义。

You will need to define what "safe" means to your standards.

安全吗？我会说几乎是的。该项目有10年的时间，有力的程序员，几个眼睛从早期alphas审查它，所以我不会指望任何主要因为beta状态滑落。

Safe as to security? I'd say pretty much yes. The project has 10 years on its back, potent programmers, several eyes that scrutinize it since early alphas, so I wouldn't expect anything major to slip there because of the beta status.

对于它是否足够靠近才能出来而不会成为蒸气软件是否安全？这是肯定的。您可以检查日常活动开发和承诺代码的人数和文档以确保它。

Safe as to whether it's close enough to be coming out and not become vaporware? That's a definite yes. You can check the daily active development and the number of people that commit to the code and docs to be sure about it. It's no "one man's project" to worry about.

对好代码投资安全吗？这也是一个。虽然没有那么多的插件或代码示例的头几个月现在为2.x，新的ORM是一个工作的快乐，更快更清洁，一旦完成你将有一个项目最近的代码库这不需要大量的重写。当然，直到它碰到RC，可能有小的API更改，你需要遵循，但没有打破阿尔法或任何需要你废弃你的代码，重新开始。一旦在RC（大概在十二月），你可能认为它像一个正常版本一样稳定。

Safe as to "good code investment"? That too is a yes. While there won't be that many plugins or code example for the first months as are now for 2.x, the new ORM is a joy to work on, much faster and cleaner and once finished you'll have a project on recent codebase that won't require major rewrites. Of course until it hits RC there might be small API changes that you will need to follow but nothing as breaking as alphas or anything that will require you to scrap your code and start over. Once on RC (most probably during December) you might as well consider it as stable as a normal release.

性能安全吗？这是一个yes。测试表明，它的速度是2.x，但有更多的提供。不必担心由于测试版状态而导致服务器关闭。它可能会在未来得到更多的优化，但如果它从2.x的同样的基础开始，这意味着它只会得到更快。

Safe as to performance? That is a yes as well. Tests show that it is as fast as 2.x but has so much more to offer. No worries about bringing your server down because of "beta" status. It might get more optimized in the future but if it starts from the same ground as 2.x it means it will only get faster.

唯一的没有如果安全被定义为坚持老试着的代码，以尽量减少每一个疯狂的风险，或者如果你有一个项目，可以依靠别人已经写的代码，并将不会再次触及，除非一切中断。

The only "no"s are if safe is defined by "stick to old well tried code to minimize every crazy risk" or if you have a project that can rely on code others have written and won't be touched again in the future unless something breaks.

这篇关于安全使用cakephp 3.0生产？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！