从 Kohana3 升级时会出现问题吗？
我想了解 KO3 即将推出的版本之间的兼容性。我听说一旦 3.1 推出，从 kohana 3.0 升级到它并不容易（Wordpress 从 2 到版本 3 的升级非常快）
如果我在 KO3 中创建我的项目（目前使用 3.0.6.2），我的项目在不破坏任何内容的情况下轻松升级到 3.1 或更高版本的可能性有多大？
如果您是 KO3 的真正专业人士或开发团队的一员，请回答。这很重要。
I would like to know about the compatibility between upcoming versions of KO3. I have heard that once 3.1 comes in, it won't be easy to simply upgrade to it from kohana 3.0 (Wordpress upgrade is pretty swift from 2 to version 3)
If I create my project in KO3 (currently using 3.0.6.2), what are the chances that my project will be easily upgradable to 3.1 or above versions without breaking anything ?
Please answer if you are a real pro on KO3 or part of the development team.. This is important.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
主要版本（例如：3.0 至 3.1）可能会更改 API。目前，最大的 API 更改是将
Request类拆分为Request和Response，以及对Request的更改> 允许外部路由。这也意味着Remote类将被显着修改以完全删除，以支持外部请求和响应。您可以按照3.1 路线图跟踪 3.1 计划的更改。
Major versions (eg: 3.0 to 3.1) may change the API. Currently, the biggest API change will be splitting the
Requestclass intoRequestandResponse, as well as changes toRequestthat allow external routing. This also implies that theRemoteclass will be significantly modified to removed completely in favor of external requests and responses.You can keep track of the changes scheduled for 3.1 by following the 3.1 roadmap.
我只想指出，wordpress 是一个完全不同的系统，它基本上是一个在自己的框架上编写的应用程序，而 kohana 只是框架，您提供应用程序。
如果 WordPress 核心框架发生变化，那么他们也会更改其应用程序以适应这些修改。有时插件在升级过程中不兼容，因此插件作者必须发布使其兼容的更新。所有这些对前端用户都是隐藏的，他们不需要知道它是如何工作的就可以使用它。
另一方面，Kohana 没有 GUI 或前端，您需要了解代码的细节。如果接口发生变化，那么您必须调整您的实现以适应，这是没有办法解决的。
正如 antpaw 所说，单元测试对于确保事情按预期工作总是有用的！有关更多信息，请参阅 unittest 存储库
I'd just like to point out that wordpress is an entirely different system, it's basically an application written on their own framework whereas kohana is just the framework and you supply the application.
If the wordpress core framework changes then they also change their application to account for those modifications. Sometimes plugins aren't compatible across upgrades so the plugin author has to release an update which makes it compatible. All of this is hidden from the front end users, they don't need to be aware of how it works in order to use it.
Kohana on the other hand has no gui or front end, you're getting nitty gritty with the code. If an interface changes then you'll have to adapt your implementation to suit, there's no way around that.
And as antpaw said, unit tests are always useful for making sure things work as expected! For more info see the unittest repo
这很大程度上取决于您使用的功能。尝试一下并观察您的日志，甚至更好：您运行单元测试。 http://github.com/kohana/core/compare/3.1... master 如果我选择了正确的存储库。这将帮助您了解 ko3.1 和 ko3.0.7 之间的区别
it highly depends on the features your have used. give it a try and watch your logs or even better: you run unittests. http://github.com/kohana/core/compare/3.1...master if i picked the right repository. this will help you to see the difference betwenn ko3.1 and ko3.0.7