Dev doc refactor release instructions #1057
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
…o release document
petersilva
requested review from
reidsunderland,
MagikEh,
tysonkaufmann and
andreleblanc11
petersilva
added
the
Documentation
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.
Hi folks, This is a bit of a re-factor of the Developer's guide. No code.
How to do a Release has actually gotten relatively far from the original vision of a totally automated process. In the developer's guide to date, all of the pieces for how to do a release were present, but it was scatterred around and a there was, as they say, some assembly required.
The new Release manual is a document solely about creating a release. It goes over:
It's very manual. If folks want to automate bits of it... Please do so, but for now, this at least documents what needs to be done to perform a software release.
It's also a lot easier to find, as I don't actually use the Developer's guide except to make releases, and I found the release information hard to find before. Now it's at least in one place, and fairly sequential.