A call for community feedback on improving the WordPress release party testing phase. The post identifies key pain points: the #core Slack channel becomes hard to follow, testing scenarios lack release-specific context, test reports are insufficiently detailed, coverage is hard to gauge, and there's no clear path for contributors after the party ends. Goals include better use of contributor time, more relevant test scenarios, structured reporting, and connecting release party testing to the broader pre-release testing cycle. With WordPress 7.0 releasing at WordCamp Asia on April 9th, the author sees an opportunity to experiment. Proposed ideas include a Learn WordPress course on release party testing, pairing newer contributors with experienced ones, a real-time testing board to track scenario coverage, and a clear 'what's next' close to each party.
Table of contents
What Makes Release Party Testing GreatCurrent Pain PointsGoalsAn Opportunity at WordCamp AsiaSummarySort: