-
Notifications
You must be signed in to change notification settings - Fork 64
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
chore: update command generator for versioned docs #335
chore: update command generator for versioned docs #335
Conversation
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.
Please see my comments above
acd359f
to
15a77ab
Compare
@FeynmanZhou I removed the bug fix release from the script and added a way to map using bug fixes if necessary. Normally, the pages won't change during a release. |
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.
LGTM although IANAM. What if we are updating 1.1 and the content of version-latest is 2.1.1?
Better add some comments or documents on how versions-latest
should be used, otherwise when someone need to refresh for a patch release, they need to read and understand below code in refresh-commands.sh
map_version() {
grep "$1" versions-latest || echo "$1.0"
}
Signed-off-by: Terry Howe <[email protected]>
15a77ab
to
dc74774
Compare
LGTM although IANAM. |
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.
LGTM. Thanks @TerryHowe
Created a mapping file in case we need to use a bug fix release to generate the docs. I don't think that will happen often. Signed-off-by: Terry Howe <[email protected]>
Created a mapping file in case we need to use a bug fix release to generate the docs. I don't think that will happen often.