define freshness tiers for F# #48008
Open
+10
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.