-
Notifications
You must be signed in to change notification settings - Fork 469
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
Remove most mentions of Core license from docs #19001
Remove most mentions of Core license from docs #19001
Conversation
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
b846378
to
7e276d6
Compare
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
@kathancox can you please look at my (hopefully minimal) changes to the backup docs in this PR? to make sure i'm not making a huge mess in your product area? 🙇 also as noted in the description i have completely left out core changefeeds while we work towards a decision there - @taroface for you this is a general review request pls 🫡 ofc feel free to opine on the backup changes as well from a writerly POV |
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.
Few comments, not sure if it is necessary to remove references of "This is an Enterprise-only feature".. if we do need to. Each of the Backup feature pages, like locality aware, encrypted etc. include a note saying this. Also, instances like this: https://www.cockroachlabs.com/docs/v24.2/backup-and-restore-overview#backup-and-restore-support (I'm not sure if the third column needs to change.)
And, instances like this "You do not need an Enterprise license to run any of the backup validation tools described on this page."
Let me know if there is anything I can do here to help. Also, I've sent a message out re Core changefeeds, will keep you up to date.
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.
Blocking here mostly for the Dedicated mention that slipped through. I have a longer comment on a separate change; sorry if you already have an upcoming plan for the things I raised! Otherwise I can raise it in Slack.
thanks @kathancox ! I have upscoped this PR to remove (almost) all such mentions of enterprise-only this and that. Basically 99% of things that link to there's a lot of changed files but the changes are mostly trivial deletions of sentences like "This is an Enterprise feature [LINK]" etc.
Removed all of those as well!
awesome thanks! PTAL at the latest commit called |
816dab6
to
6bad1ba
Compare
Thanks @taroface ! I have addressed your specific changes in the commit Re: the longer comment on a separate change / stuff we discussed in Slack earlier this week, I would like to address all those things too but I think for this specific "core deprecation" work those improvements will have to happen separately |
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, just a minor suggestion!
@jaiayu FYI this is the "remove mention of Core and Enterprise from docs" PR I mentioned in today's weekly FYI it does not talk about the new licensing, rather, it's the "rip out ~all the Core / Enterprise mentions" kind of pre-work PR |
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.
Since I was mentioned, I took a look at the includes and pages for deployment (install, orchestration, start
commands, etc) and security / authentication, and they look great to me. Thank you so much. (the build failure is a handful of newly-broken anchors)
synced with @kathancox offline and she's good with this merging i will now fix a couple broken anchors and merge |
* Backport changes from #19008 (#19106) Addresses DOC-11674 Summary of changes: - Backport changes from #19008 to v23.1, v23.2, v24.1, and v24.2 * Backport changes from #19072 (#19109) * Backport changes from #19072 Addresses DOC-11674 Summary of changes: - Backport #19072 to v23.1, v23.2, v24.1, v24.2 * Backport changes from #19031 (#19108) Addresses DOC-11674 Summary of changes: - Backport #19031 to v23.1, v23.2, v24.1, v24.2 * Backport changes from #19001 (#19103) Addresses DOC-10665, DOC-11674 Summary of changes: - Backport changes from #19001; a few manual edits were required due to a few patches that didn't merge automagically * Backport changes from #19126 (#19133) Addresses DOC-11674, DOC-11692 * Merge origin/main into 20241029-DOC-10624-backports (#19140) * Merge origin/main back into core relicensing backport branch (#19142) * Backport changes from #19002 (#19138) * Backport changes from #19002 Addresses DOC-11674 * Backport telemetry docs from #19131 (#19145) Addresses DOC-11051 * Backport upgrade license info from #19125 (#19146) Addresses DOC-11693 * Fix broken link on upgrade page include --------- Co-authored-by: Rich Loveland <[email protected]>
Addresses DOC-10665
Summary of changes:
Review and remove all mentions of Core license from docs, with the following exceptions (which will be later work):
Licensing FAQs page, which will be updated via DOC-11203
Mentions of Core Changefeeds, about which the method of removal from docs is TBD