Update release instructions #5560
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR updates two points in the release process: 1. The process for getting release notes for a stable release based on my experience of doing that for the past 2 releases. 1. It adds testing for the getting started guide. I did not remove the testing of `quickstart-java`. I do want to test scenarios and navigator and a bit of VSCode so the only potentially redundant point there is the `mvn compile` step but that verifies that Maven artifacts have been published successfully so I think it is still useful. changelog_begin changelog_end
garyverhaegen-da
approved these changes
Apr 15, 2020
Yeah I fully agree but I don’t have a solution here either. To give some frame of reference, it takes me less than an hour to run through this on two platforms. While an hour is a lot, as long as we actually do one release per week instead of 5 and we distribute the work so it’s not the same person doing it over and over, I think it’s probably acceptable at least in the short term. Not really sure what we do in the long-term, I don’t see any obvious steps in here that we could just kill. Most of them have caught bugs in the recent past. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates two points in the release process:
my experience of doing that for the past 2 releases.
testing of
quickstart-java. I do want to test scenarios andnavigator and a bit of VSCode so the only potentially redundant
point there is the
mvn compilestep but that verifies that Mavenartifacts have been published successfully so I think it is still
useful.
changelog_begin
changelog_end
Pull Request Checklist
CHANGELOG_BEGINandCHANGELOG_ENDtagsNOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines runtotrigger the build.