On the 3.8 Release:
- The merge window closed with yesterday’s dev meeting. If you missed it, you can catch the logs.
- All of the plugins mentioned in last week’s chat as candidates made it in:
- Widgets Area Chooser
- TwentyFourteen is still chugging along.
- Work continues on other development, including enhancements that were not built into plugins, which you can participate with on trac, until 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, scheduled for next Wednesday.
- We’re still deciding exactly in which manner to include Open Sans in core, and how much to bundle.
On Future Releases:
- Chats continue for The Search Initiative (Previously “Omnisearch”), which is growing in scope a bit, but in a good way.
- There is still some interest in Featured Content, but it’s in need of a lead to give it a chance to land in a future release.
- Work continues on the Front End Editor project, with regular chats on Mondays at 16:00 UTC.
On CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Standards:
- Among CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. preprocessors, SASS was chosen for use in core.
- There is broad consensus that we should begin requiring braces for if statements, even for single line blocks. This is for, at the very least, future code — although it may be applied to current code in an automated change sweep.
If you have anything to add, or there are questions on the above, please comment below!