Releases/2.1.0.m1 #27
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
ivargrimstad
approved these changes
Jun 1, 2022
|
@erdlet Did you already run the release job for the tag? |
|
No sorry. Also I removed the branch by accident, so I need to recreate a release branch bases on the tag |
|
TBH: I don't remember anymore how the releases are performed. Wasn't there a Jenkins job which publishes releases by checking out a tag and building it? In this case having the tag would be fine... |
|
Thanks to Ivar I'm aware of the procedure. Thought we want to keep the release branch. But maybe this makes only sense for RC and final releases. I'll have a look into it this evening :) |
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.
Now the correct branch for milestone release. Contains tests for form method overwrite and fixes for CDI usage