-
Notifications
You must be signed in to change notification settings - Fork 6k
Adding ms.update-cycle #46988
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
base: main
Are you sure you want to change the base?
Adding ms.update-cycle #46988
Conversation
#assign-reviewer:dominicallen |
Co-authored-by: Genevieve Warren <[email protected]>
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.
Overall, this is good. I had a couple of questions, and then it's ready.
docs/visual-basic/reference/command-line-compiler/langversion.md
Outdated
Show resolved
Hide resolved
docs/csharp/whats-new/csharp-11.md
Outdated
@@ -2,6 +2,7 @@ | |||
title: What's new in C# 11 | |||
description: Get an overview of the new features added in C# 11. | |||
ms.date: 03/15/2024 | |||
ms.update-cycle: 365-days |
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.
This folder will likely be a special case. During the preview cycle, they'll be regular updates. Once a version is complete, it's, well, complete. I don't expect to make any changes to the new features in C# 11 anymore. (Same with csharp-12.md and csharp-13.md). Those could reasonably be expected to the set to 1825 days. However, the csharp-14.md will have regular updates between now and this November.
What should we do here so that reality is reflected in our data and reports?
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.
Hey @BillWagner. Great question.
This is a perfect use case for why freshness tiers is needed, so you can mark content based on where it is in it's product lifecycle, and the likely rate of change in the docs as a result.
If you can tell us what that folder should be marked with today, we'll tag it with that (hopefully via docfx if it's the entire folder), and then you have the ability to change it whenever you need, to reflect the business requirements (keeping in mind that the reports only refresh once a month so anything more dynamic than that work be reflected).
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.
@dominicallen Thanks for the clarifications.
Let's mark the folder as 1825days
and the individual file for C# 14 (csharp0-14.md) as 180days
. Thanks.
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.
@BillWagner I set the whole docs/csharp/whats-new/ to 1825-days, removed individual values that had been set in this folder except for csharp-14.md, which I set to 180. Let me know if I'm missing anything.
Co-authored-by: Bill Wagner <[email protected]>
…docs into nl-set-update-cycle
Summary
@dominicallen
Updating freshness metadata as per https://dev.azure.com/msft-skilling/Content/_workitems/edit/434161/?view=edit
For list of update scenarios, see: https://microsoft.sharepoint.com/:x:/t/cfit/ESbbDqmHXspNsU6uJGadREIB9vChqX0wa-HOeqbOb3JXeQ?e=PMIJVi&nav=MTVfezgwRTFDMDQ3LUJBRDctNENDQS1CNEFGLThDNDRCNkFCRTNFQX0
Internal previews