Support new Spring release train versioning and suffixes

Open
#193 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, spring
Domain
release, tooling

Research direction

Start with ProjectVersionTests.should_return_true_for_a_valid_version() and run the test to reproduce the failure for 2020.0.0. Trace the project-version validation used by that test, then confirm that YYYY.MINOR.MICRO versions are accepted alongside -MX and -RCX prerelease suffixes and without a .RELEASE suffix.

Written by the indexing model from the issue text.

Description

enhancement

We are moving to calver with YYYY.MINOR.MICRO suffix for prereleases are -MX, -RCX. For release there is no longer a .RELEASE.

In ProjectVersionTests.should_return_true_for_a_valid_version() the following happens

then(projectVersion("2020.0.0-M1").isValid()).isTrue(); // success
then(projectVersion("2020.0.0-RC2").isValid()).isTrue(); // success
then(projectVersion("2020.0.0").isValid()).isTrue(); // failure
Dominant language
Java
Stars
32
Forks
24
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-cloud/spring-cloud-release-tools

All issues in spring-cloud/spring-cloud-release-tools

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.