Repository navigation
Say that a package repository releases at most once a week - #9
Draft
jwrosewell wants to merge 1 commit into
Draft
jwrosewell wants to merge 1 commit into
jwrosewell wants to merge 1 commit into
Conversation
The contributing guide for repositories without their own now says that a repository publishing packages releases rc into main at most once a week, why, which checks hold to it, and how an early release is asked for, linking to the common-ci contributing guide for the details.
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
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.
Merge together with common-ci#303, whose description says when that should reach
main. The rule starts from the date in the configuration variableWEEKLY_RELEASES_FROM, so this guide should go live with the checks it describes.What this does
The contributing guide for every repository without its own gains a section, "How often a release goes out". It says that a repository publishing packages releases
rcintomainat most once a week, so each package gets at most one new version a week, and why, which is that fewer versions are easier to keep up with and that nuget.org asks search engines not to index a package page while the oldest of its 20 newest versions is under 90 days old. It names the two checks that hold to the rule, the "Only rc into main" check on the release pull request and the publish, and says that an early release needs James Rosewell's permission and is asked for with the labelearly-releaseand a re-run of the check, because adding a label does not run it again.The section links to the new "Releasing at most once a week" section of the common-ci contributing guide, which common-ci#303 adds. The link works once that reaches common-ci's
main.How it was checked
The wording matches the checks as built and tested in common-ci#303, whose description gives the evidence for the nuget.org rule and the test runs. This change is text only.
What remains
Nothing in this repository. The changes other repositories need are listed in common-ci#303.