This post summarizes the dev chat meeting from May 17th (agenda, Slack archive).
- 4.7.5 was released; six security issues and three maintenance fixes, thanks to everyone who pitched in to get that out!
- Beta 1 went out on Friday, May 12th
- Beta 2 is due out this Friday, May 19th; potentially shepherded by @matias between 16:00 and 18:00 UTC
- Please plan anything important before Beta 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. 2 in by Thursday evening, May 18th
4.8 Bug Scrubs
4.8 Dev Notes Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. / 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.
- So far, a single Dev Note has been published
- Goal is to have them all done ASAP so we can assemble the Field Guide by RC1
- Remaining Dev Notes to get published:
- 1) Editor: TinyMCE inline element / link boundaries – @iseulde & @azaozz
- 2) Editor: TinyMCE version 4.6 – @iseulde & @azaozz
- 3) Editor: Edge fixes – @iseulde & @azaozz
- 4) Customize: Media widgets (#32417) – @westonruter
- 5) Customize: Visual text widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. (#35243) – @westonruter
- 6) Multi-site – @jeremyfelt
- 7) Changes to headings in WP Admin (and super admin) – @afercia
Location identification in Events widget
- Dashboard widget can be tested via Nearby WordPress Events plugin
- Geolocation database licensing issues tracked in #2823-meta
- Example coverage of radius maps
- Will work through UX User experience regression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. and accept a11y Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) regression via #40735 in Beta 2
- Anything outside Customize, Editor, REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/., and CLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. has lower priority focus in 2017
- Major work on other components will likely not be merged or considered