Add: Documentation for the release process.#151
Conversation
|
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. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## trunk #151 +/- ##
=========================================
Coverage 80.46% 80.46%
Complexity 178 178
=========================================
Files 20 20
Lines 1474 1474
Branches 120 120
=========================================
Hits 1186 1186
Misses 288 288
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
jonathanbossenger
left a comment
There was a problem hiding this comment.
Looks good, just one small change.
|
|
||
|
|
||
|
|
||
| Post an announcement in the #core slack channel saying a new RC version is ready for testing, and ask users/developers to report any issues found in that version. |
There was a problem hiding this comment.
Probably should be the #core-ai channel.
This PR just publictly documents the release process that we have been following for the composer package.