The following bugbug 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. scrubs have been planned for the 4.9 release:
- Monday, September 25th 11:00 CDT / Monday, September 25th 16:00 UTC by @jbpaul17 focused on enhancements and feature requests in the 4.9 milestone in #core
- Wednesday, September 27th 10:00 CDT / Wednesday, September 27th 15:00 UTC by @jbpaul17 focused on enhancements and feature requests in the 4.9 milestone in #core
- Friday, September 29th 11:00 CDT / Friday, September 29th 16:00 UTC by @jbpaul17 focused on enhancements and feature requests in the 4.9 milestone in #core
- Monday, October 2nd 10:00 CDT / Monday, October 2nd 15:00 UTC by @jbpaul17 focused on enhancements and feature requests in the 4.9 milestone in #core
- Wednesday, October 4th 11:00 CDT / Wednesday, October 4th 16:00 UTC by @jbpaul17 focused on enhancements and feature requests in the 4.9 milestone in #core
Reminder that Wednesday, October 4th is 4.9 BetaBeta 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. 1 and from that point on, no more commits for any new enhancements or feature requests will be allowed in this release cycle, only bug fixes and inline documentation. Work can continue on enhancements and feature requests not completed and committed by this point, but will not be picked up for commit again until the start of the next WordPress release cycle.
As a refresher, here’s a post from the 4.7 release cycle answering questions about bug scrubs.