SpringCloud官网： https://spring.io/projects/spring-cloud/#learn
Preface
Before using SpringCloud and SpringBoot to build a project framework, you need to understand the compatible correspondence between the two versions. I am very curious about the naming rules of SpringBoot and SpringCloud official version numbers. If you want to find out, it is obvious that the version of SpringBoot Numbers are named by numbers, while SpringCloud uses Greek and English letters. When the version is released, it is named after the London Underground Station and is named according to the first letter AZ of the subway station name.
- The first generation version: Angle;
- The second generation version: Brixton;
- The third generation version: Camden;
- The fourth generation version: Dalston;
- The fifth generation version: Edgware;
- The sixth generation version: Finchley;
- The seventh generation version: GreenWich;
- Eighth generation version: Hoxton;
The official version is released as follows:
One, Spring Boot version number
1. Example: 2.3.3. RELEASE
-
Among them 2: indicates the main version number, which means that it is our second-generation SpringBoot product. When the functional module has a major update or the overall architecture changes, the main version number will be updated.
-
Among them, 3: indicates the minor version number, some new functions have been added, but the main body's structure has not changed and is compatible, but only partial changes. .
-
Among them 3: Indicates that it is generally a bug modification or small change.
-
RELEASE: Greek letter version number. This version number user indicates which development stage the current version of the software is in
-
So 2.3.3.RELEASE together is the third bug fix version of the third minor version of the second generation version of springboot.
SpringBoot version format: major version number. sub version number. revision version number.
2. Interpretation of the Tail Greek Version Number
- snapshot: snapshot
- alpha: closed beta
- beta: public beta
- release: stable version
- GA: The most stable version
- Final: The official version
- Pro(professional): Professional Edition
- Plus: Enhanced version
- Retail: Retail version
- DEMO: Demo version
- Build: Internal label
- Delux: Deluxe Edition (deluxe: luxurious, gorgeous)
- Corporation or Enterpraise Enterprise Edition
- M1 M2 M3: M is short for milestone meaning milestone
- RC version RC: (Release Candidate), almost no new features will be added, but mainly focus on debugging
- SR: revised version
- Trial: Trial version
- Shareware: Shared Edition
- Full: Full version
Glossary:
build-snapshot: Development version, also called snapshot version. The current version is under development. After the development is completed, test it yourself, and let other people in the team also test and use it;
M1...M2 (Milestone): Milestone version, several milestone versions will be released before the release. I used the snapshot version to develop for a period of time. I feel that the code has been written recently. Then just record a few milestone versions. Recording this important moment of ours is a memory of you and my future.
RC1...RC2 (Release Candidates): release candidates. The internal development has reached a certain stage. After the integration of various modules, after careful testing, the entire development team feels that the software is stable and there is no problem, and it can be released to the outside world.
release: the official version. After the release candidates are almost the same, it means that the entire framework has reached a certain stage and can be used in a large area on the market. Then release it and let the majority of users enjoy it.
SR1...SR2 (Service Release): revised version. What does this mean? After the release version is released, it is used by the general public. No matter how powerful architects are, they can’t write code with zero bugs. At this time, fix the problems of the release version first. At this time, the version of each iteration is SR1, SR2, SR3.
The above sequence:
snapshot –>M1…MX –> RC1…RCX –> release –> SR1…SRX
Corresponding text understanding:
Development version (BS) - (Development to a small stage, you need to mark it down) --> Milestone version (MX) - (The version has reached a relatively stable stage and can be released to the outside world, but there may still be fixed problems. At this time, only repairs will be made, no new features will be added) -> Release Candidate (RC1)-(BUG repair completed, released) -> Official version (release)-(external feedback has some problems, internal repair) --> Modified version (SRX)
2. Production environment version selection
When deploying in a production environment, you must choose the most stable version of SpringCloud and SpringBoot to avoid choosing an unstable version to cause some major production accidents on the project.
1. Version selection
-
CURRENT: The currently recommended version.
-
GA: stable version, available for production
-
PRE: Milestone/Preview version
-
SNAPSHOT: snapshot
The version number is just an identification, so that you can introduce the version number when you use it. For the sake of stability, we generally choose the RELEASE, CURRENT and GA versions, and SNAPSHOT is not selected.
2. 2.4 0-M2 PRE
2.4.0: The 0th bug fix of the 4th minor version of the second-generation Spring Boot;
M2: This is the second milestone version of version 2.4.0;
PRE: Chengbei version/preview version, inform us that this is a milestone version, whoever steals the fish first can come;
3. 2.3.3 CURRENT GA
2.3.3: The third bug fix of the third minor version of the second-generation Spring Boot;
CURRENT: This is the currently recommended version of the official website;
GA: This is a stable version and can be used in a production environment.
4. 2.3.4 SNAPSHOT
2.3.4: The fourth bug fix of the third minor version of the second-generation Spring Boot;
SNAPSHOT: This is a version that we are developing internally, and it is also an iterative version of bugs for version 2.3.4;
5. 2.2.9 GA
2.2.9: The 9th bug fix of the second minor version of the first generation of Spring Boot;
GA: This is a stable version and can be used in production;
3. Version correspondence
Release train Spring Boot compatibility
| Spring Cloud Release Train | Spring Boot Version |
|---|---|
| Hoxton | 2.2.x |
| Greenwich | 2.1.x |
| Finchley | 2.0.x |
| Edgware | 1.5.x |
| Dalston | 1.5.x |
| Camden | 1.4.x |
| Brixton | 1.3.x |
| Angle | 1.2.x |
Note: Official announcements SpringBoot1.5.xand the following versions are no longer officially maintained. It is recommended that developers choose to use the SpringBoot2.0.xabove versions, and the corresponding SpringCloudversions are best not to be used.
to sum up
Tip: The choice of the version of the production environment is very important. Remember to choose the stable SpringBoot and SpringCloud versions for development.