In the previous week we didn’t run the test scrub. That’s why the agenda stays the same for this week. Early test scrub for WordPress 5.8 will take place on 2021-04-16 13:30 in the core-test channel.
We’ll do manual testing of the below tickets, making sure there are no regressions:
We’ll appreciate your participation and feedback!
What you need
- WordPress environment
- WordPress 5.8 alpha release, try the WordPress Beta Tester plugin (choose the “Bleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). Only” stream options)
- Two of the tickets are not merged yet. To test them we’ll need to set up the Testing Environment by following the steps listed here – https://meta.trac.wordpress.org/ticket/5581#comment:3
How to apply a patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.
Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket Created for both bug reports and feature development on the bug tracker., for example
npm run grunt patch:35449
How to fetch and then checkout a PR, for example, PR 828
git fetch upstream pull/828/head:pr-828
git checkout pr-828
or for PR:
npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828
Check the handbook for more ways to test patches.
Looking forward to seeing you!
#5-8, #test, #testing