Skip to content
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

Article links to TR that has actually been migrated to docs #1447

Open
1 task done
adamn-netapp opened this issue Aug 13, 2024 · 2 comments
Open
1 task done

Article links to TR that has actually been migrated to docs #1447

adamn-netapp opened this issue Aug 13, 2024 · 2 comments
Assignees

Comments

@adamn-netapp
Copy link

Page URL

https://docs.netapp.com/us-en/ontap/flexcache/index.html

Page title

FlexCache overview

Summary

This article contains a link to the old PDF version of TR-4743: FlexCache in ONTAP.

My understanding is that that TR has already been migrated to docs.netapp.com - https://docs.netapp.com/us-en/ontap/flexcache-writeback/flexcache-write-back-overview.html. We should have a link to the new docs location, not the old TR PDF.

This article also lists changes made in 9.9.1 and 9.10.1, but it doesn't mention any other changes since 9.10.1. Meanwhile, this article -- https://docs.netapp.com/us-en/ontap/flexcache-writeback/flexcache-write-back-overview.html -- talks about changes in 9.15.1.

We should update this article to include the 9.15.1 changes. While we're at it, we should check if there were others between 9.10.1 and 9.15.1. Seems a pretty long gap.

Public issues must not contain sensitive information

  • This issue contains no sensitive information.
@netapp-ehoffman
Copy link

@adamn-netapp , TR-4743: FlexCache in ONTAP has not yet been migrated to docs.netapp.com. We've published the net-new writeback content, but haven't yet migrated the remainder of the FlexCache content.

@netapp-dbagwell netapp-dbagwell self-assigned this Aug 14, 2024
@netapp-dbagwell
Copy link
Contributor

What Ed said regarding overall FlexCache TR migration. This is net new content intended to live as part of that TR. It's first out of the gate, however. @elliottecton do we need to address any gaps between releases as Adam suggests? I know you're working on hot fixes already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants