I am the p5subset updater this month. Does this mean you prefer I hold off and instead review a PR that does so? I have to admit, I am not sure what it means to review a PR that just pulls in the subset (and updates tests to match). I mean, there are no changes that can or should be made to the subset, and whether or not it breaks the Stylesheets build, it has to go in. So are you seeking a review of the changes to the expected-results/ files? (I.e., a quick thumbs up if the changes seem to be the result of changes to the subset? ’Cause there really seems to be no point in spending the entire weekend on a detailed examination of 6,400+ changes.)
the release team (Martina, Sabine and I) had a very productive morning and pulled in some pending pull requests. There are still various pending PRs but we urge you to keep your hands away from the keyboard since we already entered freeze period (i.e. the real freeze, not the hot freeze!)
That said, we’d really appreciate your input and review for/of
The first two might get into the release if approved over the weekend; the third is a necessary update of the file p5subset.xml for the Stylesheets tests. Here we need to look through the changes to the expected results and whether they correctly reflect our intentions.
The release team scheduled a meeting for Monday (see Google calendar) where we will go through the weekend-fallout. Additionally, we will then move all open issues and PRs from the current milestones to the next. If you already know about unfinished work regarding your tickets, please feel free to move them to the next milestone yourselves.