(一)Eclipse版本介紹?
??????????????????????????????????????????????????????????????????????????????????????????????????? ?作者:李紅軍???????? 6/20

可以從 eclipse.org 網站 ( http://www.eclipse.org/downloads ) 下載，可以發現『最新』與『最好』的版本，這兩種版本通常不一樣，基本上有五種版本 或建置 (build) 可供下載：

n?? ? 釋放版/正式版 (Latest Release builds) ?E.g.,3.1.2

?????????????? 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.

正式版是由Eclipse開發團隊在R1.0的基礎上所創建發布的.正式版是為那些在穩定、測試版的基礎上所創建并且最近不需要對其特性做出更新和提高的人們所服務的。正式版的名字總是以字母“R”來開頭，例如R1.0, R2.0等。非正式版的命名是根據開發版本的日期來確定的，例如：20011027就是說真個版本是在2001年10月27日所創建的。
?? 說明：由Eclipse開發團隊所宣稱的主要穩定版本。Release builds經過完整測試，并具有一致性、定義清楚的功? 能。它的定位就跟上市的商業軟件一樣。

n?? ? 穩定版 (Stream Stable ?builds) E.g., 3.2RC7

??????????????? 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.

穩定版被大多數人們認為是相當穩定的集成版。他們是由Eclipse開發團隊測試一段時間并且認為相當穩定以后從集成版到穩定版的一個提升。最新的穩定版是為那些想使用最新發展技術流并不介意由此帶來的一些新特性及bug問題所創建的人們所服務的。由于穩定版本的價值及反饋及時，最新穩定版是開發團隊比較樂意使用的版本之一。
?? 說明：比Release build新一級的版本，經由Eclipse開發團隊測試，并認定它相當穩定。新功能通常會在此過渡版本出現。它的定位就跟商業軟件的beta版一樣。?

n????? 整合版(Stream Integration ?builds)E.g., I20060614-0843

? ??? 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.

周期性地,組件團隊版脫離了他們所認為的穩定、一致狀態并且更新內建的結構來暗示下一個整合應該采取這個組件版本。整合版是從這些由每一個組件團隊認定為最適用的版本版本中發展起來的。整合版經過一段時間測試后可以提升為穩定版。當新的穩定組件版釋放的話整合版響應地建立起來。
??說明：此版本的各個獨立的組件已經過Eclipse開發團隊認定具有穩定度，但不保證集成在一起沒問題。若集成在一起 夠穩定，它就有可能晉升成Stable build。

n??? 當日最新版（ Stream Nightly ?builds) E.g., N20060617-0010

?????????? 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.

當日最新版是每天從CVS容器流產生出來的。它們完全沒有經過測試、總是有一些主要問題。許多根本上就跑不起來。通常對于Eclipse Project 在開發中是有用的。
?? 說明：此版本顯然是從最新的原始碼產生出來的。可想而知，此版本當然不保證它跑起來沒問題，搞不好還有嚴重的bug。

?n?? 維護版 (Stream Maintenance Build) E.g.,. R2_1_maintenance ， R2.1 or R2.1.2

Maintenance builds are produced periodically to incorporate fixes into an existing release. They are typically built from tagged plug-in and feature pojects 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.
???? 維護版周期性的納入現存組件來發行。它們是從現存于CVS容器維護流的有標簽的插件和特性項目中發展起來的（如? R2_1_maintenance）。它們在開發團隊認為一個或者是更多個測試點達到穩定后可以提升成為一個鏡像或者服務來釋放。

?翻譯得不好，歡迎大家多提寶貴意見！??！
?

引用參考??