Major changes in microservices spring cloud 2020

Time:2022-6-19

Starting from spring cloud 2020.0.0-m1, spring cloud has abolished the naming method of London underground station in the United Kingdom and used a new “calendar” version naming method.

Major changes in microservices spring cloud 2020

The official announcement is as follows:

https://spring.io/blog/2020/04/17/spring-cloud-2020-0-0-m1-released

What is a calendar version?

Java framework project case:www.fhadmin.cnEnglish Name: calendar versioning

The calendar version is not based on any number, but on the release date of the project. As time goes by, the version will get better and better.

This date based version naming is called calendar versioning, or simply calendar.

Detailed introduction reference:

https://calver.org/

Let’s take a look at how spring cloud began to use the calendar version.

Spring cloud usesYYYY.MINOR.MICRONaming rules for:

  • YYYY: indicates 4-digit year;
  • MINOR: represents an increasing number, starting from 0 every year;
  • MICRO: represents the version number suffix, which is the same as that used before.0be similar to.RELEASESame,.2be similar to.SR2

The suffix separator for the pre release version is also.Change to-, such as:2020.0.0-M1and2020.0.0-RC2Naming is shown in.

Meanwhile, spring cloud will stop adding to the snapshot versionBUILD-Prefix, such as:2020.0.0-SNAPSHOTNaming is shown in.

However, the naming of London underground station has not been completely abolished. Spring cloud will continue to use it as the version code. The current code is:Ilford, but the versions published to the Maven repository will no longer use these names.

Finally, let’s enjoy the naming method of new and old version numbers of spring cloud under Maven:

Old version Name:

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-dependencies</artifactId>
    <version>Hoxton.SR6</version>
    <type>pom</type>
    <scope>runtime</scope>
</dependency>

Title of new edition:

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-dependencies</artifactId>
    <version>2020.0.0-M2</version>
    <type>pom</type>
    <scope>runtime</scope>
</dependency>

I personally think it will be more convenient to use the calendar version naming method. I can more clearly see the year of the current version. I don’t know how long I haven’t upgraded when I see the alphabetic and pure numeric version numbers.

This work adoptsCC agreement, reprint must indicate the author and the link to this article