Eclipse Project Build Types

Releases

Releases are builds that have been declared major releases by the development team - for example "R1.0". Releases are the right builds for people who want to be on a stable, tested release, and don't need the latest greatest features and improvements. Release builds always have an "R" at the beginning of the name i.e. R1.0, R2.0 etc. Non-release builds are named according to the date of the build - for example 20011027 is the build from Oct 27, 2001.

Releases是由开发团队所宣称的主要发行版本，像是"R1.0"版
Releases是给那些想要使用稳定、经过测试、而且不需要最新改进功能的使用者所使用的
Releases会有一个"R"在其版本名称开头，也就是R1.0、R2.0之类的
还沒发行的版本会在其名称上标明建造日期，像是20011027就是在2001年10月27号所建造的

Stable Builds

Stable builds are integration builds that have been found to be stable enough for most people to use. They are promoted from integration build to stable build by the architecture team after they have been used for a few days and deemed reasonably stable. The latest stable build is the right build for people who want to stay up to date with what is going on in the latest development stream, and don't mind putting up with a few problems n in order to get the latest greatest features and bug fixes. The latest stable build is the one the development team likes people to be using, because of the valuable and timely feedback.

Stable为经过整合后、对一般使用者來说夠稳定的版本。
架构团队会在使用一些时日后，把认为夠稳定的Integration版本提升到Stable
最新的Stable版本是那些想使用新功能的使用者之最佳选择
为了让你可以用到好的功能与修正后的版本，不要介意把你所遇到的问题提出來
最新的Stable版本是开发团队希望使用者去使用的，因为即時的回馈对他们帮助很大

Integration Builds

Periodically, component teams version off their work in what they believe is a stable, consistent state, and they update the build configuration to indicate that the next integration build should take this version of the component. Integration builds are built from these stable component versions that have been specified by each component team as the best version available. Integration builds may be promoted to stable builds after a few days of testing. Integration builds are built whenever new stable component versions are released into the build.

开发各元件的团队会定期发布他们觉得稳定、一致性高的版本
并指出下一个Integration版本的元件要做出什么样的更新
Integration是各元件小组把他们各自觉得最稳定的元件兜在一起的版本
需要一些时日的测试他们才能把Integration版本提升到Stable版本
Integration版本里面的各个元件都各自是稳定的

Nightly Builds

Nightly builds are produced every night from whatever has been released into the HEAD stream of the CVS repository. They are completely untested and will almost always have major problems. Many will not work at all. These drops are normally only useful to developers actually working on the Eclipse Project.

Nightly是每天晚上放置到CVS中的版本
完全沒有经过测试，而且几乎都有一些問題，其中很多根本还不能用
这些版本通常只对Eclipse的开发者有用

Maintenance Builds

Maintenance builds are produced periodically to incorporate fixes into an existing release. They are typically built from tagged plug-in and feature projects in a maintenance stream of the CVS repository (i.e. R2_1_maintenance). Maintenance builds are promoted to a minor or service release (i.e. R2.1 or R2.1.2) after development teams have deemed one to be stable following one or more test-fix pass cycles.

Maintenance是定期把现有的发行修正后的版本
他们通常结合了一些plug-in与projects后放到CVS中，像是R2_1_maintenance
Maintenance加入一些小功能，并由开发团队经过一些测试與修正的周期，认为稳定后发行的