Tuesday, April 13, 2004
Eclipse各種版本介紹
本文列出Eclipse各個版本的定義與差別
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加入一些小功能，並由開發團隊經過一些測試與修正的週期，認為穩定後發行的
