因此，Drupal 6 的一个麻烦是很难将更改从开发服务器转移到测试服务器或登台服务器到生产服务器。
Drupal 7 中这变得更容易了吗？模块开发人员现在是否应该遵循一些编码约定？那么开发人员可以轻松地将内容和配置分开，并且只在开发、测试和生产之间移动配置吗？
仍然使用功能模块？
So one hassle of Drupal 6 is that it's tough to move changes from a development server to a test or staging server to a production server.
Has this been made easier in Drupal 7? Is there some coding conventions module developers are suppose to follow now. So a developer can easily separate content and configuration and only move configuration between dev, test, and prod?
Is the recommended advice to still use the Features module?
发布评论
评论（1）
据我所知，Drupal 7 中没有专门解决部署问题的附加功能。在一段时间内，功能可能仍然是解决这一系列问题的最佳解决方案。然而，Drupal 7 中的一些新功能（例如核心中的实体和字段）可能会使创建模块时更容易将其配置数据公开给功能。
To the best of my knowledge, there are no additional features in Drupal 7 that specifically address the deployment issues. Features will probably continue to be the best solution to that set of issues, for some time. However, some of the new features in Drupal 7 such as entities and fields in core may make it easier, when creating a module, to expose its configuration data to Features.