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

Update automatic-vm-guest-patching.md to indicate availability timelines for Windows Server 2025 Azure Edition #93

Merged
merged 3 commits into from
Nov 19, 2024

Conversation

kjohn-msft
Copy link
Contributor

The lists have been updated to prioritize clarity on the Hotpatchable images, and a message added on timelines for newer images.

…nes for Windows Server 2025 Azure Edition

The lists have been updated to prioritize clarity on the Hotpatchable images, and a message added on timelines for newer images.
Copy link
Contributor

@kjohn-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link

Learn Build status updates of commit 0910200:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/automatic-vm-guest-patching.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@maulikshah23
Copy link
Contributor

#sign-off

@maulikshah23
Copy link
Contributor

#approved

@Court72
Copy link
Contributor

Court72 commented Nov 15, 2024

@kjohn-msft, @maulikshah23,

The statement "Support for the following Windows Server 2025 images is currently being rolled out across the world with coverage expected everywhere by mid-December 2024" constitutes a future promise. Documentation should only describe what is possible with the released product. Can you revise the content to remove that statement?

For more information, see What can I publish on Microsoft Learn?

After you make these changes, #sign-off again to start another review.

Thanks
#hold-off

@Court72
Copy link
Contributor

Court72 commented Nov 15, 2024

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Nov 15, 2024
Removing future-looking statement
Copy link

Learn Build status updates of commit 70f4981:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/automatic-vm-guest-patching.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@maulikshah23
Copy link
Contributor

@sign-off

@maulikshah23
Copy link
Contributor

@Court72 - please see the updated text, please review and merge immediately.

@Court72
Copy link
Contributor

Court72 commented Nov 15, 2024

This PR is ready for merge. Due to the upcoming Ignite conference, all merging and publishing is on hold until the morning of the keynote address.

The PR review team will resume merging on the morning of the keynote address for the regularly scheduled daily publish cycles. You don't need to take further action on this PR; we'll merge it on the day of the keynote address.

Don't add more commits to this reviewed PR. If you need to make additional changes to these files, email techdocprs for guidance about how to proceed.

#label:"missed-content-complete","event-triaged-to-10AM"

@prmerger-automator prmerger-automator bot added event-triaged-to-10AM missed-content-complete Label used during release conference to identify PRs in content freeze labels Nov 15, 2024
Copy link

Learn Build status updates of commit a948607:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/automatic-vm-guest-patching.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Court72 Court72 merged commit 22025ef into MicrosoftDocs:main Nov 19, 2024
2 checks passed
kjohn-msft added a commit to kjohn-msft/azure-compute-docs that referenced this pull request Jan 6, 2025
… Windows Server 2025 Azure Edition

This is a timely follow up to this temporary change: MicrosoftDocs#93

Support for images in the list are available in all regions now, so the informational message is being removed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants