WordPress 4.9.5 was released a couple of weeks ago, at the scheduled time and without known issues. We (@audrasjb and @danieltj) had the pleasure to co-lead this minor release of the CMS, with @sergey‘s invaluable help as deputy and @jbpaul17’s mentorship. For this release, we were two co-leaders, contributing to the core for a short time, and none of us had core committer status. Thank you all again for trusting us for this task.
Below you will find some feedback and tips we wanted to share with you and we hope this will encourage others to get involved in such an adventure.
To lead a WordPress release, you don’t have to be a core committer,
you have to deeply care about the WordPress open-source project.
Initially, we wondered how the two of us could claim to run a WordPress release without commit access.
In fact, there are many tasks that are not related to the commit action itself, but require a good knowledge of the ecosystem, the people and teams involved and how the release process works. Here are some examples of tasks to do:
Triage: sorting tickets and status update. This is a very time consuming task, because you have to dive into each ticket, read all the
Source: https://managewp.org/articles/17348/4-9-5-feedback-leading-a-wordpress-minor-release
source https://williechiu40.wordpress.com/2018/04/22/4-9-5-feedback-leading-a-wordpress-minor-release/
No comments:
Post a Comment