-
Notifications
You must be signed in to change notification settings - Fork 128
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
832 consolidate hosted osi documentation sources #837
832 consolidate hosted osi documentation sources #837
Conversation
Signed-off-by: Philip WINDECKER (AVENYR GmbH) <philip.windecker@avenyr.de>
Signed-off-by: Philip WINDECKER (AVENYR GmbH) <philip.windecker@avenyr.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Thanks!
Just a reminder for later-me/others: To close #832 we also need a PR in this repo to cleanup the gh-pages branch (as discussed in the issue)
I just had a second look, I think we also should change the proto file:
As expected, this shows also up in the documentation. I would simply write something like:
Or if somebody really wants a reference, than point to a page that actually explains this like https://opensimulationinterface.github.io/osi-antora-generator/asamosi/V3.7.0/specification/general_docs/versioning.html (this is a fixed 3.7. link..) |
This is true and I noticed it as well. But I agree that it would be better to point to the documentation (with an updated date) and not the README (whose link is not working any longer). A fixed version, however, will only work if the version is not latest (in the current setup, at least). For now, I will go without the link. |
Signed-off-by: Philip WINDECKER (AVENYR GmbH) <philip.windecker@avenyr.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As these changes are editorial I am ok with merging this to main without a CCB. Especially as a merge to main is not equivalent to a release.
Let’s keep the spirit of Eternia alive! 🚀 @jdsika I am fine if you go ahead with the merge, we have enough members of the prior CCB that have approved this topic and the changes are editorial. |
Reference to a related issue in the repository
#832
Add a description
Remove legacy links.
Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:
If you can’t check all of them, please explain why.
If all boxes are checked or commented and you have achieved at least one positive review, you can assign the label ReadyForCCBReview!