Clarify version stepping in upgrade instructions #1804
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
mjankowski
force-pushed
the
upgrade-instructions
branch
from
dd3f791 to
aa0037d
Compare
mjankowski
force-pushed
the
upgrade-instructions
branch
from
aa0037d to
a5d85ce
Compare
Contributor
Author
|
This doc change (if accurate) potentially answers this recent question - mastodon/mastodon#37046 |
Contributor
Author
|
@andypiper I see you might some wording edits to original changes, which is appreciated. Is this one ready to go, or contingent on a head-nod from team to just confirm this is roughly the version/update policy? |
Member
|
Thanks for the prod, I was indeed waiting for someone like @ClearlyClaire to confirm but I think this is actually good enough to go, we can revise further if needed, later. I do need someone other than me to review before we can merge though, since i touched it in the meantime. |
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.
Resolves #1356 -- or at least the portion of it related to docs, some of it is more about writing release notes.
Definitely open to wording suggestions on this one ... sort of compiling this from what I believe to be roughly true from various other discussions across different issues/PRs/etc.