Document the steps necessary to cut a release #969
Merged
Conversation
This file contains 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
This is nothing new or special, but it should provide a handy checklist for cutting new releases, which in turn might cause us to do this more often. The gap between the v4.7.0 and v4.8.0 releases was about 8 months, mostly because we had some turnover in maintainers, and the new maintainers had never cut a release, so it loomed as a somewhat uncomfortable unknown. Documenting this should make it easier for new maintainers to whip up a release when it makes sense to do so.
|
Yep, that looks right. 👍 I think @tarebyte is set up to add new maintainers, but let me know if you need me to add anyone to Rubygems. |
tarebyte
approved these changes
Dec 20, 2017
|
This has been released as part of https://github.com/octokit/octokit.rb/releases/tag/v4.9.0 |
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.
This is nothing new or special, but it should provide a handy checklist for cutting new releases,
which in turn might cause us to do this more often.
The gap between the v4.7.0 and v4.8.0 releases was about 8 months, mostly because we had some
turnover in maintainers, and the new maintainers had never cut a release, so it loomed as a somewhat uncomfortable unknown.
Documenting this should make it easier for new maintainers to whip up a release when it makes sense to do so.
View rendered checklist
@pengwynn since you've probably done most of the releases until now, would you have 5 minutes to glance through this checklist and make sure I'm not missing anything?
/cc @bkeepers as unofficial cat-herder of the octokit libraries