(一)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）。它们在开发团队认为一个或者是更多个测试点达到稳定后可以提升成为一个镜像或者服务来释放。

 翻译得不好，欢迎大家多提宝贵意见！！！
 

引用参考