Improve gutenberg release docs to explain the plugin backporting process #47372
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
…herry-picking tool is used)
- Rename point to minor - Fix incorrect usage of minor, normal releases are considered major - Explain github labelling process for minor releases
talldan
added
the
[Type] Project Management
talldan
requested review from
ajitbohra,
ryanwelcher,
juanmaguitar and
fabiankaegy
as code owners
talldan
requested review from
priethor,
youknowriad,
noisysocks,
ockham and
annezazu
talldan
commented
Jan 24, 2023
|
|
||
| Once the commits have been cherry-picked, remove the `Backport to Gutenberg RC` label and update the milestone to the current release for all cherry-picked PRs. | ||
|
|
||
| If you decide that the fixes deserve another release candidate before the stable version is published, create one by following the instructions above. Let other contributors know that a new release candidate has been released in the [`#core-editor` channel](https://wordpress.slack.com/messages/C02QB2JS7). |
There was a problem hiding this comment.
This last paragraph is confusing, but I've decided to leave it as it was.
There was a problem hiding this comment.
It could use some refinement, but in general it's much clearer now.
priethor
approved these changes
Jan 24, 2023
|
|
||
| Once the commits have been cherry-picked, remove the `Backport to Gutenberg RC` label and update the milestone to the current release for all cherry-picked PRs. | ||
|
|
||
| If you decide that the fixes deserve another release candidate before the stable version is published, create one by following the instructions above. Let other contributors know that a new release candidate has been released in the [`#core-editor` channel](https://wordpress.slack.com/messages/C02QB2JS7). |
There was a problem hiding this comment.
It could use some refinement, but in general it's much clearer now.
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.
What?
Improves the gutenberg plugin release docs to explain the backporting process.
Why?
I noticed there are some errors and omissions in the docs around the backporting process for Gutenberg releases that has led to some mistakes (which were absolutely not the fault of the release coordinators—they couldn't know what isn't documented).
How?
Release candidate backports:
Backport to Gutenberg RClabel (which is a curious omission, considering there's a suggestion to use thenpm run cherry-pickscript).Minor release backports
Backport to Gutenberg Minor Releaselabel in github.Testing Instructions
Read the markdown file.