Fix old version info in release 3.3.0 #513
Merged
Conversation
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
Signed-off-by: Pierre R. Mai <[email protected]>
pmai
added
Bug
Contributor
|
(There was already a branch vom @caspar-ai regarding this.) @max-rosin: What do you think? Would it be possible to update the overview documentation in the near term? |
Contributor
|
Missing: new entry in doc/releases/v03.03.rst |
Signed-off-by: Stefan Cyliax <[email protected]>
kmeids
added
ReadyToMerge
Signed-off-by: Pierre R. Mai <[email protected]>
kmeids
approved these changes
Apr 28, 2021
kmeids
left a comment
kmeids
left a comment
There was a problem hiding this comment.
Approved from the CCB meeting 28.04.2021
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 v3.3.0 release of OSI has obsolete and wrong VERSION information of 3.2.0. In order to fix this problem we will have to release a v3.3.1 bug fix release with updated VERSION information, which this PR prepares.
A related question is whether we want to include the updated overview documentation in 3.3.1, if we have to do a 3.3.1 anyway.