-
Notifications
You must be signed in to change notification settings - Fork 477
Remove known limitations page #22325
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
base: main
Are you sure you want to change the base?
Conversation
Files changed:
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
|
❌ Cross-Version Link Check Failed Found 40 cross-version link violations that must be fixed: File:
|
❌ Deploy Preview for cockroachdb-docs failed. Why did it fail? →
|
mikeCRL
left a comment
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! Some suggestions for your consideration.
|
|
||
| {% include {{ page.version.version }}/sql/session-variable-precedence-order.md %} | ||
|
|
||
| ## Known Limitations |
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.
| ## Known Limitations | |
| ## Known limitations |
We could make this consistent with the others (sentence case), while we're here
|
|
||
| {% include {{ page.version.version }}/sql/session-variable-precedence-order.md %} | ||
|
|
||
| ## Known Limitations |
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.
| ## Known Limitations | |
| ## Known limitations |
We could make this consistent with the others (sentence case), while we're here
| <h4 id="v25-4-0-known-limitations">Known limitations</h4> | ||
|
|
||
| For information about new and unresolved limitations in CockroachDB v25.4, with suggested workarounds where applicable, refer to [Known Limitations]({% link v25.4/known-limitations.md %}). | ||
| {% include releases/v25.4/deprecations.md %} |
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.
I'm thinking we should have some note saying something like 'Known Limitations are now exclusively listed on applicable feature pages, and are no longer aggregated into a single page'.
If so, we could re-add the Known limitations heading after this, and just include that phrase there - just for v25.4 and v26.1.
WDYT?
|
|
||
| # Removed Pages | ||
|
|
||
| - destination: releases/index.md |
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.
If you go with my suggestion on v25.4.0.md to re-add the Known Limitations section to the What's New page [with a simple note under it about the change], then I think it's better to redirect to that, like this:
- destination: releases/v25.4.md#v25-4-0-known-limitations
sources: ['known-limitations.md']
versions: ['v25.4']
- destination: releases/v26.1.md#v26-1-0-known-limitations
sources: ['known-limitations.md']
versions: ['v26.1']
If not, then maybe it's better to just redirect to a search for Known Limitations: https://www.cockroachlabs.com/docs/search?query=%22Known+Limitations%22
Remove Known Limitations page on v26.1 and v25.4 as follows:
known-limitations.mdinto dedicated includes.known-limitations.mdto the Releases page. (Open to other suggestions.)known-limitations.md.