Recap: WordPress 6.7 “Rollins” Retrospective

[Editor’s note: This survey was only answered by 3 people, only 2 of which were on the release squad. It’s useful as seeing three people’s distinct opinion, but not extrapolation.]

This post summarizes the feedback received from the WordPress 6.7 retrospective. Thank you to those who contributed their feedback via the retrospective survey and comments on the post.  For ease of reading, feedback has been synthesized. Full feedback is available for review in the anonymized form responses and comments to the original post.

Please remember that the following feedback are suggestions to bear in mind for future releases rather than action items for implementation. 

What would you keep?

• Aligning Dev Chats to the time where Tech Release leads could attend was useful and should be considered in the future.
• Release process.

What would you add?

• Future release leads should be announced earlier—prior to the end of the previous release.
• More robust testing around new features in conjunction with plugins.

What would you change, reduce, or remove?

• The squad was announced too late.
• The climate of contributing.

How did the collaboration feel?

This section included ways for one to indicate how much they agreed or disagreed with a statement around collaboration.

Would you like to be part of future release squads?

What is your feedback on the current release squad size?

Takeaways and next steps

• One lead felt they and their co-leads were not appropriately respected by a sponsored non-lead and indicated their intent to not volunteer for another lead role without assurances that lead roles are to be respect by non-leads.
• Another contributor indicated a general sense that release testing throughout the cycle was less that usual.

Props to @desrosj and @jeffpaul for reviewing this post. 

#6-7, #retrospective