Dev Chat Agenda: January 30

Below is the agenda for the weekly devchat meeting on Wednesday, January 30, 2019 at 21:00 UTC:

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel in the Making WordPress Slack.

#5-1, #agenda, #core, #dev-chat

Dev Chat Summary: January 23rd

This post summarizes the weekly dev chat meeting from January 23rd (agendaSlack archive).

5.1 updates

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. 2

5.1 beta 2 went out earlier this week.

There are a few tickets still open, most of them are related to fine tuning the WSOD handling.

Schedule update

Beta 3 is scheduled for January 29, this is also the soft string freeze. All string changes must be committed by then (except for the About page).

See also: WordPress 5.1 Development Cycle

Dev notes status report

5.1 is being accompanied by a nice collection of dev notes, mainly from Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. but also from Make/Polyglots.

@desrosj is continuing to coordinate 5.1 dev notes. There are also plans to construct a 5.1 Field Guide that summarizes collects all dev notes.

Updates from focus reps and component maintainers

Meeting notes and summaries

Other calls/proposals

Open floor

The GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Team is looking for more pull request reviewers. If you’re interested, please touch base with them in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Details to be shared soon in a Make/Core Post.

About including recent Gutenberg changes in the currently scheduled releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.: the WordPress 5.1 cycle is being a bit stricter about non-regressionregression 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. 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. fixes landing during the beta period, but WordPress 5.2 is expected to be able to take bug fixes during the WordPress beta period.

About the recent Post concerning the bulk edit process: many relevant opinions and thoughts were shared during the meeting.

  • @matt expressed a desire to reopen the tickets closed in the recent bulk edit.
  • @desrosj and @jeffpaul will work on a strategy for reverting closed tickets that have not been changed since the bulk edit, to allow the tickets to be properly evaluated for closure.
  • Component maintainers to review related tickets (via this custom query). However, the 5.1 release is probably going to delay the ability to do that.
  • Contributors can also use this Trac report (replacing “myusername” with their username and scrolling to those updated on January 4th) to find the tickets they have been involved with that were affected by the bulk closing.
  • A stale keyword and/or status was discussed as a good way to leave tickets open long term and avoid closing them as wontfix and maybelaterstatuses.
  • A post on Make/Core is coming next week to kick off the efforts of the new Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Team.

This Dev Chat Summary post is open for further comments and discussions.

#5-1, #dev-chat

Dev Chat Agenda: January 23rd

Below is the agenda for the weekly devchat meeting on Wednesday, January 23, 2019 at 21:00 UTC:

  • 5.1 updates:
  • Updates from focus leads and component maintainers.
  • Open floor.

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel in the Making WordPress Slack.

#5-1, #agenda, #core, #dev-chat

Dev Chat Agenda: January 16th

Do you like devchat? I like devchat. This is the agenda for the weekly devchat meeting on Wednesday, January 16 2019 at 2100 UTC:

  • WordPress Leadership is expanding! @chanthaboune and @joostdevalk are excellent people, wonderful contributors for whom I have immense respect, and it’s exciting to see WordPress maturing as an organisation. 🙂
  • 5.1 updates:
    • There’s a new schedule update.
    • Call for triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.: there are two reports you can help work through: un-milestoned issues, and open bugs.
    • Dev notes status report.
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ documentation update.
  • Updates from focus leads and component maintainers.
  • Open floor.

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

This meeting is held in the #core channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#5-1, #agenda, #core, #dev-chat

Dev Chat Summary: December 19

Dev Chat Scheduling

Here’s a reminder that the normal meeting won’t be happening on December 26, though there are likely to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. folks around to answer questions for an open floor session. We’ll resume normal dev chats on January 2.

5.0.2 Update

WordPress 5.0.2 has just been released! Thank you to everyone who contributed.

5.0.3 Schedule and Scope

The following timeline has been proposed for WordPress 5.0.3:

  • Release Candidaterelease 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).: January 7, 2019.
  • General ReleaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.: January 9, 2019.

There have been some bugs reported in the MIME type handling changes in 5.0.1, these would be good to fix in 5.0.3. Additionally, there are 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. fixes in the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor which could also land.

5.0.3 will need a release leadRelease Lead The community member ultimately responsible for the Release.: if you’re able to help out, please comment on this post, or reach out directly.

5.1 Schedule and Scope

Feedback on the proposed WordPress 5.1 schedule has all been positive, so let’s lock it in!

Milestone Dates

  • 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: January 10, 2019
  • Release Candidate 1: February 7, 2019
  • General Release: February 21, 2019

The primary feature focuses for 5.1 will be the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 upgrade notice and pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party error protection, and block editor enhancements.

There have been some minor features already merged into trunktrunk 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., but nothing that will need to be reverted.

#dev-chat #summary

Dev Chat Summary: December 12th

Dev Chat Scheduling

As many folks will be away over the Christmas/New Year period, the next few meetings will be as follows:

  • December 19: Normal meeting.
  • December 26: Normal meeting will not be happening. There are likely to be coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. folks around to answer questions for an open floor session.
  • January 2: Normal meeting.

5.0.2 Schedule and Scope

Please note that WordPress 5.0.1 has just been released, so any previous mentions of scope or schedule for WordPress 5.0.1 should now be read as applying to WordPress 5.0.2.

WordPress 5.0.2 is intended to be released two weeks after WordPress 5.0, which would makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. date December 20. To give a little more space before the Christmas/New Year holiday period, I’ve proposed that it be released December 19.

Milestone Dates

  • Release Candidaterelease 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). 1: December 14, 2018
  • Release Candidate 2 (if needed): December 17, 2018.
  • General Release: December 19, 2018.

The following items are in scope for the 5.0.2 release:

  • Gutenberg 4.7 was released today, the fixes in this pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party release will also be in WordPress 5.0.2.
  • Twenty Nineteen bugs and visual issues.
  • There are a few PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 7.3 compatibility fixes to be made.

Any other tickets currently milestoned for 5.0.2 will be considered on a case-by-case basis, priority will be given to tickets with patches, testing, screenshots, and any other relevant information to show that they’re ready to land immediately.

5.1 Schedule and Scope

As there are already over 200 tickets fixed in WordPress 5.1, I’d like to propose that WordPress 5.1 has a relatively short release cycle.

Milestone Dates

  • 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: January 10, 2019
  • Release Candidate 1: February 7, 2019
  • General Release: February 21, 2019

A key point from the WordPress 5.0 cycle was that it demonstrated the value of having a hard feature freeze at beta 1, as well as string freezes and strict 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. fixing policies during the release candidate phase. With that in mind, I’d like to propose that we retain these policies for the WordPress 5.1 cycle.

The tickets already fixed in WordPress 5.1 need to be reviewed, to ensure they’re all stable for release in this cycle.

Apart from that, the PHP upgrade warnings and the White Screen of Death protection from the Sitesite (versus network, blog) Health Check project are currently the only uncommitted features scheduled for WordPress 5.1. The PHP upgrade warnings are currently soft warnings, ahead of the minimum PHP version bump proposed for April 2019.

@matt will be continuing his role as release leadRelease Lead The community member ultimately responsible for the Release. into WordPress 5.1. Any other feature proposals will need to be approved by him.

Please leave feedback on this post, so the scope and schedule can be confirmed in the next day or two.

Focus and Component Updates

REST APIREST 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/.

The REST API group will be re-opening discussion around authentication solutions. They’ll be posting further information about this project on make/core.

Core JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.

The Core JS group didn’t meet this week, due to many folks travelling home from WCUS. They’ll be resuming normal meetings next week.

Core Themes

The current themes focus is on triaging Twenty Nineteen issues for 5.0.2, as well as preparing to move activity from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ into TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. This move will likely happen immediately after 5.0.2.

#5-0-1, #5-0, #5-1, #core, #dev-chat #summary

Dev Chat Agenda: December 5th (5.0 Week 10)

This is the agenda for the weekly devchat meeting on December 5th, 2018 at 21:00 UTC:

  • 5.0 Planning and Updates
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

This meeting is held in the #core channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#5-0, #agenda, #core, #dev-chat

Dev Chat Agenda: November 28th (5.0 Week 9)

This is the agenda for the weekly devchat meeting on November 28th, 2018 at 21:00 UTC:

  • 5.0 Planning and Updates
    • A discussion about getting #11973 in 5.0 has been requested. https://github.com/WordPress/gutenberg/pull/11973
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

This meeting is held in the #core channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#5-0, #agenda, #core, #dev-chat

Dev Chat Summary: November 21st (5.0 Week 8)

This post summarizes the dev chat meeting from November 21st (Slack archive).

5.0 Planning and Updates

  • Gutenberg 4.4 and WordPress 5.0-beta5 shipped, including updates to the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor, PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 7.3 support, and Twenty Nineteen.
  • The 5.0 / GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ team continued their daily updates to Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., noting PRs and issues remaining, as well as recent and upcoming pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party releases (see 11/16, 11/19, 11/20).
  • There are a few pending tasks in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. needing attention, which meant release candidaterelease 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). didn’t happen yet. On the Gutenberg side, milestones are clear after 4.5.1 was released early in the day. Anyone who can commit or review, it would be great to get your attention on those remaining Trac tickets as a priority. Find out more in the post just released today.
  • The documentation reorganisation is merged and new documentation is being added. There are a couple of excellent outlines available for users and site maintainers as well as designers and developers.

Focus and Component Updates

  • The PHP team shared last week’s meeting recap with notes on Servehappy, adding support for PHP version requirements to themes, and beginnings of coordination with the Theme Review team.
  • The JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. team shared this week’s meeting recap with notes on correcting package global names and npm packages publishing workflow.
  • The Privacy team met earlier today, so only their agenda is currently available that covers 5.0 testing/patches, 3rd party code on wp.org footers, mobile app permissions and tracking, Google Fonts in Gutenberg, and Google reCAPTCHA 3.0. A full recap will be posted soon.

Announcements and Open Floor

  • The date of the release candidate and the WordPress 5.0 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. was discussed. The primary goal is to finish the RC, then decide upon an appropriate release date.
  • @aaroncampbell asked for volunteers to help onboard people, and guide them to first bugs for non-Gutenberg work at WCUS. Please reach out to him if you’re able to help.

Next Meeting

The next meeting will take place on Wednesday, November 28 21:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on the upcoming agenda post so that we can take them into account.

#5-0, #core, #dev-chat, #summary

Dev Chat Agenda: November 14th (5.0 Week 7)

This is the agenda for the weekly devchat meeting on November 14th, 2018 at 21:00 UTC:

  • 5.0 Planning and Updates
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

This meeting is held in the #core channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#5-0, #agenda, #core, #dev-chat