define freshness tiers for F# #48008
Conversation
Define freshness tiers for different folders in the F# guide. I followed the general strategy I used for C#: Areas that are likely to need updates for each release based on new features are 1 year. Most reference is 3 years: Someone should give it a look, even if it's not likely that new features impact it. Some of the reference for stable features is 5 years. Compiler diagnostics are 10 years.
|
@T-Gro Can you give this a once over. The new metadata here determines when an article gets flagged in reporting for a mandatory edit pass. The more "stable" an article is, the longer that duration can be. For example, I doubt existing compiler diagnostics would go away, or be emitted for new reasons. Those are the longest value. Language reference is somewhat longer because of the high backwards compatibility bar we have. (Other signals tell when to update a page here for new features). Our get started and conceptual material should change more often because any feature might impact our recommendations for given scenarios. |
|
Hi @BillWagner , I will do a rough assessment. |
Co-authored-by: Tomas Grosup <tomasgrosup@microsoft.com>
Define freshness tiers for different folders in the F# guide.
I followed the general strategy I used for C#: Areas that are likely to need updates for each release based on new features are 1 year. Most reference is 3 years: Someone should give it a look, even if it's not likely that new features impact it. Some of the reference for stable features is 5 years. Compiler diagnostics are 10 years.