Instead of a digital version, the SpringCloud main project version is named in English.
Similar to Android, which uses the names of oreos and lollipops, SpringCloud takes the same approach, choosing the names of London underground stations and naming them with the first letters a-Z
The version number
Large version of Spring Cloud | Large version of Spring Boot | instructions |
---|---|---|
Angel | Compatible with Spring Boot 1.2.x | Not recommended |
Brixton | Compatible with Spring Boot 1.3.x and Spring Boot 1.4.x | Not recommended |
Camden | Compatible with Spring Boot 1.4.x and Spring Boot 1.5.x | Not recommended |
Dalston | Compatible with Spring Boot 1.5.x, incompatible with Spring Boot 2.0.x | Not recommended |
Edgware | Compatible with Spring Boot 1.5.x, incompatible with Spring Boot 2.0.x | Retired on 2019/08/01 |
Finchley | Compatible with Spring Boot 2.0.x, incompatible with Spring Boot 1.5.x | Request jdk1.8 |
Greenwich | Compatible with Spring Boot 2.1.x | It is recommended to use |
Hoxton | Compatible with Spring Boot 2.2.x | Current version to M2 |
As mentioned above, Spring Cloud Edgware has been retired and Finchley is the main release of Spring Boot 2.0.x. The Finchley life cycle will also be terminated by the termination of Spring Boot 2.0.x. Therefore, Greenwich edition is only recommended for learning or using.
Small version number
Spring Cloud version | The Spring version of the Boot |
---|---|
Finchley.M9 | . 2.0.0 RELEASE |
Finchley.RC1 | 2.0.1. RELEASE |
Greenwich.BUILD-SNAPSHOT | 2.1.8. BUILD – the SNAPSHOT |
Greenwich.RELEASE | 2.1.2. RELEASE |
Greenwich.SR1 | 2.1.3. RELEASE |
Greenwich.SR2 | 2.1.5. RELEASE |
Version Number Meaning
Spring Cloud is in a state of rapid iteration, with different stages of development corresponding to different release numbers. A large release starts with build-snapshot, which represents a SNAPSHOT release. The code in this release is not fixed, but is in flux.
When development reaches a certain level, say 50%, an MX version will be released, he said. For example, M1 represents the first milestone release
After several milestone releases, we are ready to release release candidate (RCX), which provides a release watch period for the official release and fixes bugs. RC1 represents the first release candidate
After one or more RELEASE candidates, a RELEASE is released
After the official release, if any errors or bugs are found, the SRX version will be released after the fix, also called the official release.
conclusion
The version number | meaning |
---|---|
BUILD-SNAPSHOT | Snapshot version, the code is not fixed, is in flux |
MX | Milestone version |
RCX | Release candidate |
RELEASE | Official Release |
SR2 | Official Release |
mark | meaning |
---|---|
CURRENT | Current recommended version |
GA | Stable version, available for production |
PRE | Milestone version |
SNAPSHOT | The snapshot |
Query the mapping between SpringCloud and SpringBoot versions
Here is a joke about the official website. The version mapping on the official website of Spring is always updated, rather than added. For example, on 2019/08/21, the version mapping on the official website is like this
The official’s bad display strategy adds a great obstacle for us to find the corresponding relationship of historical editions, which leads us to infer the corresponding relationship of published books from the clues of netizens’ bodatabase and the official website
First of all, there’s this website that has a bit of json that looks like this
In other words, the versions of Spring Cloud and Spring Boot are not one-to-one, but Spring Boot can be used as long as it meets a certain version range. This seems to have been said officially only in the big version, but not in the small version. This has led me to assume that a specific Spring Cloud version corresponds to only a specific Spring Boot version.
So how do we know the Spring Boot release range for each Spring Cloud release? Can refer to the website above, above the website does not have, to tell the truth I also did not find
Use official documents to find version mappings
If you can’t find the version you’re looking for, check the official documentation.
Select this one and you can see the whole thing
Look for spring-boot-starter-parent in this, as mentioned in section 88.5.1
In the Greenwich.SR2 document, the version of spring-boot-starter-parent is 2.1.6.RELEASE, while the official website says 2.1.5.RELEASE. Which one to believe?
In fact, both versions can be used. As mentioned above, the versions of Spring Cloud and Spring Boot are not one-to-one, but they can be used as long as they meet a certain version range.
If you can’t find a historical version of the document, find a web address and change the URL
Find a corresponding relationship so troublesome, in the final analysis or the official work did not do well