Docs: split "Gutenberg Release Process" page into two #71130
Improve index page
- Loading branch information
commit 9435a3f785af376086c0c3a9796f9db681a4a80d
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,11 +1,9 @@ | ||
| # Gutenberg Release Process | ||
|
|
||
| The [Gutenberg repository](https://github.com/WordPress/gutenberg) on GitHub is used to perform several types of releases. This page links to guides for the different release processes that happen in the Gutenberg project. | ||
|
|
||
| Before you begin, there are some requirements that must be met in order to successfully release a stable version of the Gutenberg plugin. Both [plugin releases](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/) and [the publication of packages](https://developer.wordpress.org/block-editor/contributors/code/release/package-release-and-core-updates/) require the following. You will need to: | ||
|
|
||
| - Be a member of the [Gutenberg development team](https://developer.wordpress.org/block-editor/contributors/repository-management/#teams). This gives you the ability to launch the GitHub actions that are related to the release process and to backport pull requests (PRs) to the release branch. | ||
| - Have write permissions on the [Make WordPress Core](https://make.wordpress.org/core) blog. This allows you to draft the release post. | ||
| - Obtain approval from a member of the Gutenberg Core team in order to upload the new version Gutenberg to the WordPress.org plugin directory. | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this could be treated more like an table of contents/index page that links to the other two pages and maybe has a very brief summary of the different kinds of releases.