Update release instructions; make independent of legacy docs #2053
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
This documents the release process I've been doing since this app launched as the main Zulip mobile app.
These are lightly adapted from the version that was in the legacy app's doc, with updates where needed.
This cuts another dependency on the legacy app's instructions.
Adapted from the legacy app's version mostly by updating the discussion of our beta practices. Also putting this section at the end, to avoid cluttering the way to the main instructions that we use on each release.
Logically these sections come before the main instructions, as they're needed before one can follow those. It's convenient to keep the main instructions handy right at the top, though, because we consult them much more often. So these links help make it comfortable to maintain that inversion.
…mplete This was the last piece of information where this doc relied on a reference to the legacy app's documentation.
chrisbobbe
force-pushed
the
pr-release-instructions
branch
from
3e55efb to
e710508
Compare
Collaborator
|
Thanks, looks great! Merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 resolves a TODO item which had been at the top of this doc since launch, and should simplify following the instructions for future releases.
Selected commit messages:
10c0017 docs/release: Finish updating release instructions to reflect main app
This documents the release process I've been doing since this app
launched as the main Zulip mobile app.
1adc810 docs/release: Incorporate terminology section on alpha/beta/prod
Adapted from the legacy app's version mostly by updating the
discussion of our beta practices. Also putting this section at
the end, to avoid cluttering the way to the main instructions
that we use on each release.
9ebff09 docs/release: Add pointers at top to terminology and setup sections
Logically these sections come before the main instructions, as
they're needed before one can follow those. It's convenient to keep
the main instructions handy right at the top, though, because we
consult them much more often. So these links help make it
comfortable to maintain that inversion.
3e55efb docs/release: Incorporate alpha/beta instructions; declare updates complete
This was the last piece of information where this doc relied on a
reference to the legacy app's documentation.