ACE minor/major/micro release的区别<转>

modern

The ACE+TAO+CIAO Release Process
Minor releases of ACE+TAO+CIAO occur periodically, typically twice a year. Minor releases have two-digit numbers, e.g., 5.3. Major releases are released infrequently, typically once a year. Major releases are 1-digit numbers, e.g.,5, that include substantially new functionality. Both major and minor releases are carefully tested on all platforms the ACE+TAO run on. In particular, we do not put out major or minor releases of ACE+TAO+CIAO until all the compilations and regression tests work successful on all the platform we support.
ACE+TAO+CIAO的Minor release版本会定期发布，一般一年两次。Minor release版本由两个数字组成，例如5.3。Major release版本则发布的不是很频繁，一般一年一次。Major release版本只有一个数字，例如5，通常包含了有价值的新功能。Major和Minor release版本都在所有ACE+TAO运行的平台上进行了精心测试。特别地，在在我们支持的所有平台上完成所有编译和回归测试通过前，我们是不会将ACE+TAO+CIAO的Major或Minor release版本发布出来。
Between major/minor releases, we release micro releases periodically, e.g., 3-4 times per year, so that ACE+TAO+CIAO users can download and test our latest work in progress. ACE+TAO+CIAO micro release kits have three-digit numbers, e.g., 5.3.1. Micro releases often contain important fixes that aren't in the major/minor releases and will compile cleanly and pass most tests on most platforms. They are not, however, necessarily concerned with ensuring API compatibilities between micro releases, e.g., new features may be changed or removed between the micro releases.
在发布Major/Minor release版本期间，我们还会定期发布Micro release版本，例如，每年3至4次，这样可以使ACE+TAO+CIAO的用户可以下载和试用我们工作中的最新劳动成果。ACE+TAO+CIAO release kit由三个数字组成，例如，5.3.1。Micro release版本经常包含一些没有加入到Major/Minor release版本的重要修改，它们都通过了无告警的编译和在大多数平台上的大部分测试。但是在Micro release版本间不会关心API的前后兼容性，例如，在Micro release版本间可能会有新特性的改变和删除。
The first micro release following a major/minor release is called the bug-fix-only (BFO) micro release. As the name implies, this micro release only has fixes for the most recent major/minor releases. Types of fixes and checkins that are allowed to go in for the BFO include bug fixes in the implementation; fixes to the build systems like Makefiles, project files, and MPC files; adding new tests and examples; fixes to the documentation, etc. Fixes that are definitely not allowed include changes to the public interface, refactoring implementations, removing files from the repository, adding new files into the repository, etc. The idea is to allow commercial support vendors to stabilize the major or minor release for their product offerings. As always, if you require 100% predictable stability and support, please contact one of the companies that provides commercial support for ACE+TAO.
发布在Major/Minor release版本后的第一个Micro release版本称为bug-fix-only(BFO) micro release版本。就像这个名字中所内含的意思，这个Micro release版本是用来修复最近发布的Major/Minor release版本中的bug的。可以放到BFO中的修复和检查类型包括实现上bug的修复，像Makefile、工程文件、MPC文件这一类的编译系统的修改，添加一些新的测试或样例，文档的修改等。规定不允许修改的有：对public interface和refactor实现的修改，添删repository中的文件等。这样做的目的是为了允许商业支持厂商们在他们提供的产品中使用Major/Minor release的稳定版本。就像经常出现的那样，如果你需要100%的可预言的稳定性和支持，请联系为ACE+TAO提供商业支持的公司。