Today’s dev chat, starting in two hours:
- Triage https://core.trac.wordpress.org/report/5. No ticket Created for both bug reports and feature development on the bug tracker. should be without an owner, a path forward, and a timeline.
- Discuss timeline for RC1 and how we are all feeling.
- Things we need to do (or start thinking about) to prepare for a final release:
- We need an About page of features. So, what are our wins?
- Continue to scan the support forums and awaiting review tickets reported against trunk to ensure we don’t miss anything.
- Brainstorm what features and API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. changes need written tutorials (the “field guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.”), and get people on board to research and write them.
- Figure out what changes might need “3.5 compat” posts. The wpdb::prepare() argument change comes to mind, and obviously parts of media.
All tickets should have people responsible for them, but also, so should all of these release preparation tasks. There’s something in there for everyone — bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. gardeners, documentation, research, testing, etc.