What is Spring Cloud version control

In this issue, the editor will bring you about what is Spring Cloud version control. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

To avoid confusion with subprojects, the release train has a name, but no version. These names are in alphabetical order (so you can arrange them in chronological order), as well as the names of London subway stations ("Angel" is the first version and "Brixton" is the second version). When point releases for a single project accumulate to a critical amount, or if there is a critical bug that needs to be available to everyone, the release sequence will introduce a "service release" whose name ends with "service release". Where "X" is a number.

Hoxton (8th Generation)

Greenwich (7th Generation)

Finchley (6th generation)

Edgware (5th Generation)

Dalston (first 4)

Bxxx (second generation)

Axxx (1st generation)

Greenwich.SR2,SR2 means Service Release bug fix, 2: the first official version of Greenwich.Release Greenwich version, the first bug fix version of Greenwich.SR1 Greenwich version

Release order

Greenwich.Release-- > Greenwich.SR1-> Greenwich.SR2

The above is the editor for you to share what is Spring Cloud version control, if you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.