This post summarizes the dev chat meeting from January 11th (agenda, Slack archive).
4.7.1 Update
2017 Release Schedule
- 4.7.1 will NOT be last in the 4.7 branch, so it’s best to start on anything that needs to go in 4.7.2 immediately
- Proposal from @samuelsidler:
- Since we don’t have a set release date for WordPress 4.8, I’d like to propose we look at applicable 4.7.x issues about once a month, and decide if we should ship a release.
- For 4.7.2, I think we should take a look at issues at the beginning of February, during devchat, and decide if the issues warrant a release, then ship about a week later.
- That would mean we’d be looking at a release around February 14, but we’d update the schedule after looking at the specific issues.
- We’d want to evaluate issues the week of February 6 and make a call.
- I think we said regressions and minor bug fixes are okay in 4.7 at the moment, but we can evaluate other fixes on a case-by-case basis.
- General agreement on approach, though date for 4.7.2 to be confirmed in February
- Plan to choose someone soon to lead 4.7.2, maybe at or before next week’s devchat, to keep things moving along. @jnylen0 @aaroncampbell @voldemortensen @swissspidy interest in leading that or future releases. If you have interest, ping @samuelsidler as he’s compiling a list of those interested.
-
@davidakennedy: I’d imagine we’ll package up default theme updates more in minor release. Though, we can also release those whenever to .org. I’d like to think through a schedule for that. Maybe looking at things monthly, and making a decision.
Trac Tickets
-
#39309: Secure WordPress Against Infrastructure Attacks
-
@paragoninitiativeenterprises: propose making it a point of focus for 4.8
-
@aaroncampbell: may not fit as a focus for 4.8, since those should be in the editor, customizer, and API areas. But good to talk about and try to figure out steps forward.
-
@paragoninitiativeenterprises: recommend against punting too far into the future
-
@samuelsidler: let’s think through how to implement it and work on patches for that, then decide which release to put it in
-
@westonruter: Security and performance hardening are ongoing and not limited to focuses
-
@paragoninitiativeenterprises: would like to see this land ASAP, will work on a patch with necessary tests and any necessary back-compat and post to the ticket
-
#38418: Add telemetry (aka usage data collection) as opt-in feature in core)
-
@lukecavanagh: thoughts from the group?
-
@brechtryckaert: personally in favor of usage data collection, but we’ll need to be very upfront about it upon release to avoid criticism; also worried what the impact would be on loading times/slowdown due to communication with the servers that store the data, would all depend on the way it’s implemented.
-
#39157: Feed returns 404 when there are no posts
-
@stevenkword: looking for feedback on approach on adding new conditionals and what to do now. Issue was addressed in 4.7 but caused a regression and code was reverted for 4.7.1. After 4.7.0 landed, before the reversion, an updated patch was committed that resolved the regression, but it introduced new getters to WP_Query.
-
@stevenkword: would like to find a resolution for this for 4.7.2, but need some opinions how to solve it.
- Will ping @peterwilsoncc and @dd32 to look at it
#4-7-1, #core, #dev-chat, #summary
