Added kernel-release-notes.md

[craigloewen-msft]

Added a page to track kernel release notes.

Open question:

• How do we want to indicate which kernel version is being sent to appropriate Insiders next?

[opbld30]

Docs Build status updates of commit 8aa59cf:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
WSL/kernel-release-notes.md	⚠️Warning		Details

WSL/kernel-release-notes.md

• Line 5: [Warning-author-not-found] Invalid value for author: 'crloewen' is not a valid GitHub ID

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld30]

Docs Build status updates of commit 0b67e8c:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
WSL/kernel-release-notes.md	⚠️Warning		Details
WSL/toc.yml	✅Succeeded

WSL/kernel-release-notes.md

• Line 5: [Warning-author-not-found] Invalid value for author: 'crloewen' is not a valid GitHub ID

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 027f552:

✅ Validation status: passed

File	Status	Preview URL	Details
WSL/release-notes.md	✅Succeeded

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit 0d15506:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
WSL/kernel-release-notes.md	⚠️Warning		Details

WSL/kernel-release-notes.md

• Line 5: [Warning-author-not-found] Invalid value for author: 'crloewen' is not a valid GitHub ID

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld33]

Docs Build status updates of commit 1cc8f08:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
WSL/kernel-release-notes.md	⚠️Warning		Details
WSL/toc.yml	✅Succeeded

WSL/kernel-release-notes.md

• Line 5: [Warning-author-not-found] Invalid value for author: 'crloewen' is not a valid GitHub ID

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld31]

Docs Build status updates of commit 6880adc:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
WSL/kernel-release-notes.md	⚠️Warning		Details
WSL/toc.yml	✅Succeeded

WSL/kernel-release-notes.md

• Line 5: [Warning-author-not-found] Invalid value for author: 'crloewen' is not a valid GitHub ID

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld30]

Docs Build status updates of commit f4eac8c:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
WSL/kernel-release-notes.md	⚠️Warning		Details
WSL/toc.yml	✅Succeeded

WSL/kernel-release-notes.md

• Line 5: [Warning-author-not-found] Invalid value for author: 'crloewen' is not a valid GitHub ID

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[opbld33]

Docs Build status updates of commit 8dccb9b:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
WSL/kernel-release-notes.md	⚠️Warning		Details
WSL/toc.yml	✅Succeeded

WSL/kernel-release-notes.md

• Line 5: [Warning-author-not-found] Invalid value for author: 'crloewen' is not a valid GitHub ID

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel