Update roadmap links for upcoming releases#179
Conversation
updating links to the roadmap releases to reflect the newer editions.
|
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. |
There was a problem hiding this comment.
Pull request overview
Updates the “Call for Testing” handbook page to reference the most recent WordPress roadmap/planning posts so contributors can use up-to-date sources when deciding what to test.
Changes:
- Replaced older roadmap examples (5.9–6.1) with newer release references (6.9–7.1).
- Normalized the affected list/paragraph formatting so the content renders as intended in Markdown.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| If you want to help with calls for testing and you don’t have a specific feature you’re working on in mind, there are a few sources to pull from for insight around what would be most impactful to test. When in doubt, it’s always a good idea to ask in the open what folks would like more testing help on in the [Core Dev and Core Editor meetings](https://make.wordpress.org/meetings/). Otherwise, here are sources to examine: | ||
|
|
||
| - Features on roadmap posts for releases often shared 3-4 months before a release ([5.9](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/), [6.0](https://make.wordpress.org/core/2022/01/26/preliminary-roadmap-for-6-0/), [6.1](https://make.wordpress.org/core/2022/06/04/roadmap-to-6-1/)). | ||
| - Features on roadmap posts for releases often shared 3-4 months before a release ([6.9](https://make.wordpress.org/core/2025/07/28/roadmap-to-6-9/), [7.0](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/), [7.1](https://make.wordpress.org/core/2026/06/19/roadmap-to-7-1/)). |
| - Quotes/videos/images/etc to contextualize the more quantitative feedback and examine the broader experience being tested. | ||
|
|
||
| In terms of format, this will vary based on what’s being tested. For example, you might want to group related feedback for a feature under a heading (“General Usability feedback”) or you might want to keep things more general (“General Usability feedback”). Here’s an [example of a more general summary](https://make.wordpress.org/test/2021/12/16/fse-program-site-editing-safari-summary/) and an [example of one with more specific headings](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/) based on common groupings of feedback. No newline at end of file | ||
| In terms of format, this will vary based on what’s being tested. For example, you might want to group related feedback for a feature under a heading (“General Usability feedback”) or you might want to keep things more general (“General Usability feedback”). Here’s an [example of a more general summary](https://make.wordpress.org/test/2021/12/16/fse-program-site-editing-safari-summary/) and an [example of one with more specific headings](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/) based on common groupings of feedback. |
updating links to the roadmap releases to reflect the newer editions (6.9, 7.0, 7.1).