Sync release-0.6 branch with what is in the 0.6.2-12 RPM#368
Merged
jmrodri merged 3 commits intoopenshift:release-0.6from May 28, 2020
Merged
Sync release-0.6 branch with what is in the 0.6.2-12 RPM#368jmrodri merged 3 commits intoopenshift:release-0.6from
jmrodri merged 3 commits intoopenshift:release-0.6from
Conversation
Member
|
/lgtm |
This file contains hidden or 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
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.
The 0.6.2-12 RPM release was apparently made from the
release-0.7branch by mistake back in 2018.The
release-0.7commits are belowThe current
release-0.6commits look like this:So the only commits that I saw that were in
release-0.7when0.6.2-12was tagged and built are the following commits:The
Automatic commit of package...commits have.specfile%changelogchanges that I will pick up when I do atito tagand release of therelease-0.6branch.