Spring Cloud Azure tasks for a new Spring Boot release

Background

When Spring Boot release a new version, Spring Cloud Azure team should do something to supported latest release version.

Spring boot have the following types of versions:

• BUILD-SNAPSHOT: Current development release.
• M[number]: Milestone release.
• RC[number]: Release Candidate.
• RELEASE: GA, for General Availability.

You can refer to Spring Projects Version Naming to get more information.

Tasks For Each Release

Snapshot Release

We don't need to do anything about this kind of release.

Milestone Release And Release Candidate

• Create a new issue to track the following tasks. Sample: #27864.
• Create draft PR to upgrade external dependencies' version according to spring-boot-dependencies and spring-cloud-dependencies. Refer to related readme
• Run tests by commands:
  • /azp run java - spring - tests
  • /azp run java - cosmos - tests
  • /azp run java - keyvault - tests
• Fix the test failures.
• Close draft PR.

Sample PR: #24670.

GA Versions

• Before azure-sdk-for-java in band release

  • Create a new issue to track the following tasks. Sample: #27863.
  • Read spring boot release notes. Sample: Spring-Boot-2.6-Release-Notes. Write down items we(Spring Cloud Azure team members) should care about. Just write these items by adding a new comment in the GitHub issue created in previous step.
  • Upgrade external dependencies' version according to spring-boot-dependencies and spring-cloud-dependencies. Refer to related readme. NOTE: This step should be finished before Core code complete. You can get more information about Core code complete in the Email with subject like APRIL Release Kickoff.

• After azure-sdk-for-java in band release.

  Update spring-boot and spring-cloud version in these places:

  • azure-spring-boot-samples
  • /sdk/spring/CHANGELOG.
  • Reference doc.
  • MS docs.
  • Wiki page: Spring Cloud Azure Timeline
  • Wiki page: Spring Versions Mapping
  • Wiki page: Spring Support Multiple Versions