spring-cloud-release-tools
spring-cloud-release-tools copied to clipboard
Tools used for the Spring Cloud release process
We shouldn't deploy during tests.
We should add a link to the GitHub project for the release in the blog post text
https://www.youtube.com/watch?app=desktop&v=38AYeNGjqg0
Recent example with Sleuth. For `3.0.0-M5` I removed the `spring-cloud-starter-zipkin` however I've forgotten to remove it from the BOM. We could try to resolve each of the entries from the...
We tend to forget about checking start.spring.io after we make a release. We either * should have an automated check for the Initlizr to see if the current release is...
We are moving to [calver](https://calver.org/) 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 ```java then(projectVersion("2020.0.0-M1").isValid()).isTrue(); // success...
``` Cloning repo from [https://github.com/spring-cloud/spring-cloud-static] to [/tmp/releaser-1596234662661-0/spring-cloud-static ``` I don't think this is needed anymore now that we deploy to docs.spring.io
Example https://github.com/spring-cloud-samples/sleuth-issues/commit/ee4ec9579510bc414639e7f969ccaa8aa6ec4e4c
It would be good to have the ability to show the end of life for a given project/release train via an endpoint in spring-cloud-info