Update release management guidelines #8
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
3 tasks
|
First pass looks pretty darn good. Had some trouble verifying this step:
but that's attributable to freedomofpress/securedrop#5530, not a flaw in the docs here. Still, will want to verify that functionality prior to finalizing review. |
|
Marking as ready now that freedomofpress/securedrop#5520 is merged. |
zenmonkeykstop
approved these changes
Sep 29, 2020
zenmonkeykstop
requested changes
Sep 29, 2020
eloquence
force-pushed
the
release-mgmt
branch
from
42cd9c5 to
a74db7d
Compare
|
(Squashed into one commit) |
Merged
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.
Status
Ready for review.
This fleshes out the guide for collaborating with the Communications Manager on a release, including the preparatory steps of creating a docs PR with release-specific upgrade instructions.
It also encapsulates the one trade-off with our current branching/tagging strategy: in some cases, we may have to create a release-specific branch to ensure we don't pick up documentation changes in
mainthat are not yet releasable. This is likely to be rare, but it can happen.This PR also includes a small README update to clarify that this repository is no longer in beta.