Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"For SVM disaster recovery for SVM migration" table should start with most recent ONTAP versions

Open Beginner friendly
#2,149 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The change is to the 'For SVM disaster recovery for SVM migration' compatibility table on the page linked in the issue (compatible-ontap-versions-snapmirror-concept). Open that topic's source and find the table, then compare it with the other version tables in the same topic to match their ordering. Done when the source and destination ONTAP versions are listed newest to oldest, starting with 9.19.1, and the rendered page reads consistently with the other tables.

Written by the indexing model from the issue text.

Description

Page URL

https://docs.netapp.com/us-en/ontap/data-protection/compatible-ontap-versions-snapmirror-concept.html

Page title

Compatible ONTAP versions for SnapMirror relationships

Summary

For better readability, please reverse the sort order of ONTAP source and destination in the table to be "newest -> oldest".
i.e. Start with 9.19.1 at the top/left.

Changing the sort order also makes it consistent with the other tables in this topic, too...

Thanks,
-Andris

Public issues must not contain sensitive information
  • This issue contains no sensitive information.
Dominant language
No language data
Stars
39
Forks
87
Avg merge
2h 1m
Merged PRs (30d)
11

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NetAppDocs/ontap

All issues in NetAppDocs/ontap

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.