Handbook: Detail the Gutenberg release post process #32429
Conversation
gziolo
left a comment
gziolo
left a comment
There was a problem hiding this comment.
It looks good to me. Thank you for adding more details to how the process works in practice 👍🏻
I think @youknowriad is the best person to perform another review.
ntsekouras
left a comment
ntsekouras
left a comment
There was a problem hiding this comment.
Always great to see such enhancements! Thanks @priethor 💯
|
|
||
| #### 4. Running the performance tests | ||
|
|
||
| Your post should also include a performance audit at the end, comparing the current Gutenberg release with both the previous one and the latest WordPress major version. You can use `bin/plugin/cli.js perf` to automatically do this for you by passing as parameters the tags to run the performance suite against, such as `bin/plugin/cli.js perf release/x.y release/x.z wp/a.b` |
There was a problem hiding this comment.
I think now we have a job that is run on CI that gives you the results, so there's no need to run this on your own in theory.
There was a problem hiding this comment.
As far as I see there is such a job, although it failed for the 10.7.0 to 10.7.4 releases when running the perf tests on the 5.7 branch.
There was a problem hiding this comment.
I think @mcsf updated the job to use the latest WP release as base branch which should in theory make it more stable.
There was a problem hiding this comment.
Indeed, I failed to add that it should be fixed in 10.8 thanks to #32244 👍
Description
Updates the Gutenberg release process handbook page to expand the "Writing the Release Notes and Post" based on the last release iterations.