This post summarizes the dev chat meeting from November 9th (Slack archive).
- Dev Chat timing: The Chat remains at 20:00 UTC. Daylight Savings Time means that 20:00 UTC may be a different time for you already, or it may be a different time soon. However, next week we will be at 21:00 UTC.
- Schedule: Today is the target for 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. 3! That leaves us one week until the Release Candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)., where the list of tickets must be at zero. It is currently at 32, down from 74 last week.
- Tickets: For any tickets you’ve moved into the milestone, please make sure these are active tickets, with some kind of activity every day.
- Bug Scrubs: @Helen is running regular scrubs this week.
- 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.: These will be compiled into 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. this weekend.
- Would like to see near daily scrubs for now until RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). of report 6 and of the “Defects Awaiting Review, reported against trunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.” section of report 40
- @helen, @jorbin, and @jbpaul17 are all trying to run scrubs just about everyday, but everyone should also be scrubbing
- Media, 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 Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. component teams are all actively running scrubs as well
Dev Notes / Field Guide for 4.7
- Dev Notes will be compiled into the Field Guide this weekend. Any that still need to be written should ideally be done immediately.
- List of Dev Notes expected:
- Customizer Summary – @westonruter and @celloexpressions
- Twenty Seventeen – @davidkennedy
- Images – @mike @joemcgill
- Removal of the automatic fallbacks for generating alt – @joemcgill
- Locale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. switching – @swissspiddy
- User language – @swissspiddy
- Editor – @azaozz
- Multisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site – @jeremyfelt
- PDF Thumbs/Preview – @mike
- WP_List_Util – @swissspidy
- Resource hints – @swissspidy
- WP_Taxonomy – @swissspidy
- Post Type Labels – @swissspidy
- Starter content – @helen
- Migrate into custom css – @goergestephanis
- Likely to go out on Thursday morning instead of today, although given time zones and such we should operate on “it’s happening today” anyway
- We are at 32 open tickets. Would love to see us get down to 20.
- Work/tickets that folks would ideally like to resolve for Beta 3:
- #38522: HTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. Errors on Upload with Certain PDFs
- #38726: REST API: `unfiltered_html` and slashing: terms
- #38672: Custom CSS Cascading Style Sheets. should work with existing Jetpack custom CSS
- #38541: Allow starter content to apply in a new theme when switching from another theme containing changes
- #38660: Customizer: Edit shortcuts buttons: consider to don’t use flexbox
- #38700: REST API: Cannot send an empty or no-op comment update
- #38720: REST API: Updating a comment without sending content is valid, but unsupported
- Starter content
- Video headers
- Please remember that with RC comes string freeze, so if you have any strings you think need to freeze, now is the time to get them in
- We should be closing 4-5 tickets a day in order to hit RC on Tuesday.
- Please keep testing, and working on patches.