(readme.md) Document the new process for releasing point releases for old release branches #49968
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
… branches/versions of Gutenberg
fullofcaffeine
requested review from
ajitbohra,
ryanwelcher,
juanmaguitar and
fabiankaegy
as code owners
2 tasks
fullofcaffeine
added
the
[Type] Developer Documentation
fullofcaffeine
force-pushed
the
document/new-process-for-releasing-old-point-releases
branch
from
12a85e1 to
01a381c
Compare
|
Flaky tests detected in 5ff32d7. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5488864530
|
ockham
reviewed
Jul 6, 2023
ockham
approved these changes
Jul 6, 2023
Co-authored-by: Bernie Reiter <[email protected]>
fullofcaffeine
deleted the
document/new-process-for-releasing-old-point-releases
branch
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?
Document the new process to release point (minor) releases for old release branches/versions of Gutenberg that's implemented in #49082.
Why?
The new process is implemented in #49082 as changes in a couple of GH workflows and the release documentation should hence be updated to reflect those changes.
How?
By adding a new section explaining the new process and removing the old paragraph that said old minor release were not possible if a new release branch was already created.
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast