-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs/release/23.2 #18
Merged
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
The version will be determined by the playbook.
The failing build can be ignored until we merge the pull requests in the individual components. |
This was referenced Nov 3, 2023
The build is failing. It seems to be the case, because it uses the |
odzhychko
commented
Nov 6, 2023
mhuster23
approved these changes
Nov 6, 2023
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 fixes the links in the documentation.
To achieve that, I created separate release branches (eg.
docs/release/...
) for documentation in each repository.Compared to the previous tags, they have a name, that indicates a documentation release (eg. new
docs/release/23.2
vs. oldmodelix-23.2
).Those documentation release branches can be fixed independently without modifying the release tag, which indicates the version of the software. (That is what I needed to do, to make the documentation build)
We could also use documentation release tags, if you see a reason for it. Personally, I agreed with Antoras statement about the drawbacks of tags for releases:
See https://docs.antora.org/antora/latest/content-source-versioning-methods/#version-content-using-tags
Related
It relates to and should be merged after:
It relates to newly created, branches that can be reviewed, but do not need to be merged:
Side notes
Regarding this topic, I added two points to our weekly:
23.0
and23.1
?