介绍Spring-Cloud的版本是如何定义的

骑猪看日落 2024-04-18 21:30 19阅读 0赞

学习完springboot之后收获很多，之后准备转战springcloud，众所周知，springboot是对spring框架的封装，简化了配置的复杂度，spring-colud是一种云端分布式架构解决方案，基于spring boot,在spring boot做较少的配置，便可成为 spring cloud 中的一个微服务。

![watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L20wXzM3NzMyODI5_size_16_color_FFFFFF_t_70][]

学习之初，我对springcloud的版本号关系产生了困惑，它到底怎么命名的，其实很简单，哈哈。

Spring Cloud是一个由众多独立子项目组成的大型综合项目，每个子项目有不同的发行节奏，都维护着自己的发布版本号。Spring Cloud通过一个资源清单BOM（Bill of Materials）来管理每个版本的子项目清单。为避免与子项目的发布号混淆，所以没有采用版本号的方式，而是通过命名的方式。

这些版本名称的命名方式采用了伦敦地铁站的名称，同时根据字母表的顺序来对应版本时间顺序，比如：最早的Release版本：Angel，第二个Release版本：Brixton，然后是Camden、Dalston、Edgware，Finchley，Greenwich，目前最新的是Hoxton版本。

当一个版本的Spring Cloud项目的发布内容积累到临界点或者解决了一个严重bug后，就会发布一个“service releases”版本，简称SRX版本，其中X是一个递增数字。当前官网上最新的稳定版本是Greenwich SR2。

以下是spring官网对springcloud的介绍：

Spring Cloud is an umbrella project consisting of independent projects with, in principle, different release cadences. To manage the portfolio a BOM (Bill of Materials) is published with a curated set of dependencies on the individual project (see below). The release trains have names, not versions, to avoid confusion with the sub-projects. The names are an alphabetic sequence (so you can sort them chronologically) with names of London Tube stations ("Angel" is the first release, "Brixton" is the second). When point releases of the individual projects accumulate to a critical mass, or if there is a critical bug in one of them that needs to be available to everyone, the release train will push out "service releases" with names ending ".SRX", where "X" is a number.

<table> Table 1. Release train Spring Boot compatibility 
 <thead> 
 <tr> 
 <th>Release Train</th> 
 <th>Boot Version</th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td> Hoxton </td> 
 <td> 2.2.x </td> 
 </tr> 
 <tr> 
 <td> Greenwich </td> 
 <td> 2.1.x </td> 
 </tr> 
 <tr> 
 <td> Finchley </td> 
 <td> 2.0.x </td> 
 </tr> 
 <tr> 
 <td> Edgware </td> 
 <td> 1.5.x </td> 
 </tr> 
 <tr> 
 <td> Dalston </td> 
 <td> 1.5.x </td> 
 </tr> 
 </tbody> 
</table>

<table> Table 2. Release train contents 
 <thead> 
 <tr> 
 <th>Component</th> 
 <th>Edgware.SR6</th> 
 <th>Greenwich.SR2</th> 
 <th>Greenwich.BUILD-SNAPSHOT</th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td> spring-cloud-aws </td> 
 <td> 1.2.4.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-bus </td> 
 <td> 1.3.4.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-cli </td> 
 <td> 1.4.1.RELEASE </td> 
 <td> 2.0.0.RELEASE </td> 
 <td> 2.0.1.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-commons </td> 
 <td> 1.3.6.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-contract </td> 
 <td> 1.2.7.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-config </td> 
 <td> 1.4.7.RELEASE </td> 
 <td> 2.1.3.RELEASE </td> 
 <td> 2.1.4.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-netflix </td> 
 <td> 1.4.7.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-security </td> 
 <td> 1.2.4.RELEASE </td> 
 <td> 2.1.3.RELEASE </td> 
 <td> 2.1.4.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-cloudfoundry </td> 
 <td> 1.1.3.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-consul </td> 
 <td> 1.3.6.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-sleuth </td> 
 <td> 1.3.6.RELEASE </td> 
 <td> 2.1.1.RELEASE </td> 
 <td> 2.1.2.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-stream </td> 
 <td> Ditmars.SR5 </td> 
 <td> Fishtown.SR3 </td> 
 <td> Fishtown.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-zookeeper </td> 
 <td> 1.2.3.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-boot </td> 
 <td> 1.5.21.RELEASE </td> 
 <td> 2.1.5.RELEASE </td> 
 <td> 2.1.8.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-task </td> 
 <td> 1.2.4.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-vault </td> 
 <td> 1.1.3.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-gateway </td> 
 <td> 1.0.3.RELEASE </td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-openfeign </td> 
 <td>&nbsp;</td> 
 <td> 2.1.2.RELEASE </td> 
 <td> 2.1.3.BUILD-SNAPSHOT </td> 
 </tr> 
 <tr> 
 <td> spring-cloud-function </td> 
 <td> 1.0.2.RELEASE </td> 
 <td> 2.0.2.RELEASE </td> 
 <td> 2.0.3.BUILD-SNAPSHOT </td> 
 </tr> 
 </tbody> 
</table>

Greenwich builds and works with Spring Boot 2.1.x, and is not expected to work with Spring Boot 1.5.x.

Note: The Dalston release train will [reach end-of-life][] in December 2018. Edgware will follow the end-of-life cycle of Spring Boot 1.5.x.

The Dalston and Edgware release trains build on Spring Boot 1.5.x, and are not expected to work with Spring Boot 2.0.x.

参考链接:

[springcloud][]

[watermark_type_ZmFuZ3poZW5naGVpdGk_shadow_10_text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L20wXzM3NzMyODI5_size_16_color_FFFFFF_t_70]: https://image.dandelioncloud.cn/pgy_files/images/2024/04/18/62d8d9e2e32e4200a4664abf1946feaa.png
[reach end-of-life]: https://spring.io/blog/2018/06/19/spring-cloud-finchley-release-is-available
[springcloud]: https://spring.io/projects/spring-cloud