-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Improve plugin release checklist and documentation #70808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
2. `npx lerna updated` | ||
> Example | ||
> | ||
> ```shell | ||
> npx lerna updated | ||
> @wordpress/e2e-tests | ||
> @wordpress/jest-preset-default | ||
> @wordpress/scripts | ||
> lerna success found 3 packages ready to publish | ||
> ``` | ||
Example: | ||
```shell | ||
npx lerna updated | ||
@wordpress/e2e-tests | ||
@wordpress/jest-preset-default | ||
@wordpress/scripts | ||
lerna success found 3 packages ready to publish | ||
``` |
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.
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.
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Flaky tests detected in b0a1cd5. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/16407703365
|
Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Thanks @t-hamano ! There is currently plenty of release documentation, which is great, but on the other hand, one recurring piece of feedback I hear from first-timers is that it can be overwhelming. Is there anything you would simplify both in the docs and the issue template? |
Hi @priethor, To be honest, it was a lot of work to read every section of the documentation to prepare for the release 😅 I believe we can simplify the documentation a bit more while still keeping the information accurate. I'll consider submitting a PR to update the documentation after the 21.3 release is complete. |
What?
This PR improves the issue template and documentation to make it easier to release the Gutenberg plugin release.
Why?
I’ll be leading the Gutenberg release for the first time in 21.3, but I want to make sure that contributors like me who are leading a release for the first time don’t get lost.
How?
Issue Template
https://github.com/WordPress/gutenberg/issues/new?template=New_release.md
{UPPER_CASE}
formatDocumentation
https://developer.wordpress.org/block-editor/contributors/code/release/
Testing Instructions
Check the new issue template:
https://github.com/WordPress/gutenberg/blob/docs/update-release-process/.github/ISSUE_TEMPLATE/New_release.md
Check the new document:
https://github.com/WordPress/gutenberg/blob/docs/update-release-process/docs/contributors/code/release.md