Tag Archives: 5.2.1

Justin Ahinon 6:20 am on June 6, 2019
Tags: 5.2.1, , ,   

Dev Chat Summary: 05 June

@desrosj facilitated a lively discussion with a number of contributors.

Announcements

@chanthaboune posted earlier today about new material to help Team Leads get going. If you’d like to get started leading WordPress teams, check out her material and feel free to ask questions or leave comments. The link is https://make.wordpress.org/updates/2019/06/03/team-lead-interest-post.

Upcoming Releases Discussion

Point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.

@audrasjb, co-lead of 5.2.2, outlined some points about the small number of tickets for the milestone. Since more than 60 tickets are committed in 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./5.3, the release team suggested looking at landing some of those in the minor. The criteria, per the release handbook: tickets need to be self-contained and may not add new functions/files/filters to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

As a result, we have made some minor adjustments to the schedule:

  • 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: Monday, June 10, 2019, 8:00 PM GMT
  • Bug scrub: Thursday, June 06, 2019, 5:00 PM GMT
  • Release Candidate 2: Thursday, June 13, 2019, 5:00 PM GMT
  • Final Release: Tuesday, June 18, 2019, 5:00 PM GMT

Major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.

@desrosj reminded the group that @chanthaboune is still working on the logistics for the next major.

Got a ticketticket Created for both bug reports and feature development on the bug tracker. targeted for the milestone? Watching a few you’re really interested in? The team invites you to keep on scrubbing!

Call from Component Maintainers

Nothing major to say here

Open Floor

The theme review team is looking for a person with management skills to help accomplish goals and keep track of ongoing tasks.

If that interests you, please check this post out: https://make.wordpress.org/themes/2019/06/05/theme-review-team-meeting-agenda-for-11-june-2019

Some contributors asked for extra attention on these tickets:

#5-2-1, #5-3, #dev-chat, #summary

Anthony Burchell 9:40 pm on May 22, 2019
Tags: , 5.2.1, , , ,   

Dev Chat Summary: 22 May

@chanthaboune served as the facilitator for discussion and many contributors were in attendance.

Announcements

Nothing major to announce this week. Tune in next!

5.2.1 Debrief

WordPress 5.2.1 released yesterday! For information on the release you may refer to the 5.2.1 blog post. Thanks to @desrosj and @earnjam for leading such a smooth release. As of now, there are no notable issues. If you are seeing any issues, please discuss in the comments below or create a new ticketticket Created for both bug reports and feature development on the bug tracker. at: https://core.trac.wordpress.org/.

5.2.2

There are a handful of tickets in the 5.2.2 milestone. A team is needed to help wrangle those tickets into a new release. Now is the time to volunteer for leading 5.2.2. This release would aim to be for a 2 week release cycle to clear up remaining tickets in the milestone. There were two volunteers to lead in chat today: @audrasjb and @justinahinon. Please volunteer in the comments below if you are also interested in leading or co-leading!

@aduth said there was mention of a few issues in #core-editor chat earlier today of 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/ bugs which would be nice to aim to include for the release: https://wordpress.slack.com/archives/C02QB2JS7/p1558530408162500

Major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. (5.3)

Comments were closed today in the call for 5.3 tickets post. @chanthaboune will be pulling those together the submissions and do some outreach to maintainers that have not included items to the post as we prepare for the next major release. These tickets will inform what focuses this release will have.

Calls from component maintainers

@azaozz, is continuing to plan for some recommended changes and focuses for the Uploads and Media components.

@desrosj reminded us that the following components: General Component, Comments, Pings/Trackbacks, External Libraries, Filesystem APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., Rewrite Rules, and Script Loader are all currently without any maintainers. If those parts of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. interest you, feel free to reach out to @chanthaboune to get involved!

@karmatosed mentioned that there is an editor component triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. on Friday at 17:00 UTC, @desrosj and @karmatosed will be running it in #core-editor and the triage will focus on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets.

@johnbillion asked if there were any component maintainers looking for new maintainers of their components and @chanthaboune made the important reminder, “open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. is designed to let people move in and out of volunteer positions as needed” If you are not comfortable saying in dev chat that you would like to make changes, please feel free to reach out privately to @chanthaboune or other co-maintainers.

Open Floor

There was an ask by @afragen to have a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. review https://core.trac.wordpress.org/ticket/46938 He also reminded us committers are not the only ones with valuable feedback. Please direct any thoughts about the issue to the ticket, even if you are not one. 🙂

#5-2, #5-2-1, #5-3, #dev-chat, #summary

Jonathan Desrosiers 6:50 pm on May 22, 2019
Tags: , 5.2.1, , , ,   

Dev Chat Agenda: May 22

Below is the agenda for the weekly devchat meeting on Wednesday, May 22, 2019, 2000 UTC.

  • Announcements
  • 5.2.1 Debrief
  • 5.2.2 Planning
    • Call for release leads
  • 5.3
  • Calls from 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.

#agenda, #devchat

#5-2, #5-2-1, #5-3, #core, #dev-chat

Jonathan Desrosiers 6:00 pm on May 20, 2019
Tags: , 5.2.1,   

WordPress 5.2.1-RC2

WordPress 5.2.1-RC2 is now available for testing!

There are two ways to test the newest WordPress 5.2 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).: try the WordPress Beta Tester 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 (you’ll want to select the “point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. nightlies” option), or you can download the release candidate here (zip).

What’s in this release?

In addition to the everything included in RC1, 5.2.1-RC2 fixes 3 issues discovered by those who tested RC1:

  • #47323 prevents a fatal error that occurs when upgrading to 5.2.1 from WordPress < 5.2.
  • #47304 fixes a 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. that can affect the accuracy of <lastBuildDate> in feeds.
  • #47312 changes the string used on the About page for 5.2.1 to one that is already translated.

You can browse the full list of changes in 5.2.1 on Trac.

What’s next?

Committers: The dev-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) still applies when making any changes to the 5.2 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The official 5.2.1 release is still scheduled for Tuesday, May 21.

Happy testing!

#5-2, #5-2-1, #releases

Jonathan Desrosiers 7:41 pm on May 17, 2019
Tags: , 5.2.1,   

WordPress 5.2.1-RC1

WordPress 5.2.1-RC1 is now available for testing! But, your help is needed to test!

There are two ways to test the WordPress 5.2 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).: try the WordPress Beta Tester 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 (you’ll want to select the “point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. nightlies” option), or you can download the release candidate here (zip).

What’s in this release?

5.2.1 contains 32 high priority 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 and regressions, improvements 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, accessibilityAccessibility 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), i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., and polishes the Site Health feature introduced in 5.2. Here are some changes of note:

  • #47180: An issue typing in the block editor while using a RTL language has been fixed.
  • #47186: An bug causing 32-bit systems to run out of memory when using sodium_compat was fixed.
  • #47189: The “Update your plugins” link in Site Health now links to the correct page in multisitemultisite 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 installs.
  • #47185: An issue in wp_delete_file_from_directory() where files were not deleting on Windows systems has been fixed.
  • #47205: A bug was fixed where spaces could not be added in the Classic Editor after pressing shift+enter.
  • #47265: 2 fatal errors on the error protection page when a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher error was encountered in a drop-in (such as advanced-cache.php) were fixed.
  • #47244: wp_targeted_link_rel() has been improved to prevent instances where single and double quotation marks were incorrectly staggered.
  • #47169: PHP/MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. minimum version requirement checks now return proper error codes when requirements are not met in test environments.
  • #47177: The backwards compatibility of get_search_form() was improved.
  • #47297: The accuracy of the HTTPHTTP 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. requests test in Site Health was improved.
  • #47229: TinyMCE has been updated to version 4.9.4.

You can browse the full list of changes on Trac.

What’s next?

Committers: The dev-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) should now be enforced when making any changes to the 5.2 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The official 5.2.1 release is scheduled for Tuesday, May 21.

Happy testing!

#5-2, #5-2-1, #releases

Aaron Jorbin 9:40 pm on May 15, 2019
Tags: 5.2.1, , , ,   

Dev Chat Summary: 15 May

@chanthaboune served as the facilitator for discussion and a bevy of contributors participated.

Announcements

Make sure to participate in the 5.2 release retrospective!

Gutenberg Developer docs now live in DevHub!

Upcoming Releases Discussion

Point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. (5.2.1)

@desrosj has offered to be the leader of this point release, assisted by @earnjam. Many emojis welcomed William to the release leadRelease Lead The community member ultimately responsible for the Release. club.

The 5.2.1 milestone in trac should accurately reflect priorities. Anything not marked as high priority is “puntable”. Currently targeting RCrelease 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). on Thursday or Friday this week with a release on Monday or Tuesday next week.

5.2.2 remains a possibility depending on how thing shake out from 5.2.1, what the schedule for 5.3 looks like, and the tickets that remain open after 5.2.1.

Major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. (5.3)

The call for 5.3 tickets is posted. It will remain open through the weekend, so team reps and/or component maintainers will have a little time.

Next week the component maintainers should review the tickets in that thread, and then a date for 5.3 will become the target.

Calls from component maintainers

@azaozz, the maintainer for “Upload” is planning to do a “refresh” there. Mostly dev tickets that can be unblocked and fixed. He’s going to come up with a list and share it.

Open Floor

The question of if it made sense to have New Contributor office hours in #core-editor. This question was largely ignored in favor of talking about open issues, but @jorbin came in at the end to say yes since the more it is easy to contribute, the more contributors there will be.

The number of open issues in the editor component was discussed with issues being somewhat fragmented between 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/ GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ and tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. @aduth suggested using one of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor scrubs each week to focus on the trac tickets. @karmatosed volunteered to organize such a scrub along with @desrosj. It will take place May 24, 2019 at 17:00 UTC in #core-editor

Along the same lines, the question of how to support the classic editor was brought up. In general, no enhancements will be added to it and bugs should be tracked in trac.

#5-2-1, #5-3, #dev-chat, #summary

Tammie Lister 9:10 pm on May 8, 2019
Tags: 5.2.1,   

Dev Chat Summary: May 8th

Announcements

WordPress 5.2 was released yesterday! Thank you, everyone, who was involved in any aspect. @chanthaboune has some learnings from this release to take into handbook updates.

Global WordPress Translation Day is coming up on Saturday!

Planning next releases

@chanthaboune outlined a proposed plan of one small scale point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. in a few weeks and then 5.3. The suggestion was mid-August. This sparked a discussion on what could be added to the next release. It was noted component maintainers and teams are over the next few weeks going to decide what they want to achieve. @jeffpaul added that it’s worth checking which of our 9 focuses could be the star of 5.3.

Some of the suggested things to include:

  • Fine tuning recovering mode (@pbiron)
  • Anything else which gets us closer to bumping min PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher version (@pbiron)
  • Modernizing our CSSCSS Cascading Style Sheets. base (@marybaum)
  • Revisiting responsive images (@kadamwhite)

@youknowriad mentioned there is some are still some uncertainties that need to be figured out about the widgets screen + CustomizerCustomizer 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., but it would like to be in 5.3.

Regarding the mid-August timeline, it was noted a lot of Europe shuts down for extended holidays and it is common vacation time.

@mapk noted if there was no later release a lot of the bigger ticketticket Created for both bug reports and feature development on the bug tracker. items for 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/ wouldn’t make it in, so there would need to be a later one. December having a release would fit into the end of year version bump for PHP minimum to 7.x.

@chanthaboune noted to keep an eye out on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for a post and discussion.

5.2 Retrospective post

There will be one and a call for volunteers to manage was made. This will be a post on make/core asking 3 questions. @marybaum volunteered to help with that.

Calls from component maintainers

@afragen raised that if theme compatibility testing were desirable, at some point, #meta3781 needs to progress.

Open floor

Component maintainers

@afercia would like to see an audit of component maintainers and try and get new contributors involved there. @garrett-eclipse suggested a flag that could automatically be raised once someone has consistently contributed to a component, or create a potential shortlist of candidates. @jeffpaul noted this is what should happen with component maintainers. It was also noted by several people this wouldn’t help those who don’t contribute via patches.

@jeremyfelt added some thoughts on component maintaining. He noted inactive doesn’t mean unavailable and there is something to be said for historic knowledge. That said, fresh maintainers are great. Some components are just not active enough right now, which also isn’t a bad thing.

The discussion moved to talk about establishing an emeritus role and @chanthaboune linked to her post about this. It would be good to identify right now what components are in “maintenance mode” and what are “accepting features”, to get a clear picture. @jorbin noted in core we have precedence for this emeritus status.

Other open floor

@bgermann wanted to raise #21022 as something that needs a review and decision on whether a candidate for 5.3.

@clorith mentioned 5.2 hasn’t had many reports yet in forums. Some hosts have a few more than usual. There are some reports of theme updates failing after 5.2 that need investigating.

@jorbin suggested for next week getting a report of PHP versions that people using 5.2 are running. Checking back on this every month after would be great in lead up to changes end of the year. @azaozz recommended adding to the stats page and @melchoyce linked it.

@afercia wanted to discuss the a11yAccessibility 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) audit by WPCampus / Tenon and spoke on behalf of the accessibilityAccessibility 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) team. The team is glad to see the aggressive triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., but the report outlined broader, fundamental, issues in the overall design of Gutenberg. Next Friday (May 10th) there will be a discussion on this and everyone is welcome at 15:00 UTC in #accessibility.

#5.3, #devchat, #summary

#5-2-1