Upgrade/Install component bug scrub for WordPress 5.6

As part of the 5.6 release, we’ll be hosting a Upgrade/Install focused 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. scrub this Thursday, September 17, 2020, 18:00 UTC in the #core-auto-updates channel on 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/..

They are many tickets for this component that will need feedback and help to move forward, as part of WordPress 5.6 release cycle.

During the scrub, we’ll go through this TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. report:

https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&type=defect+(bug)&component=Upgrade%2FInstall&group=priority&col=id&col=summary&col=type&col=status&col=owner&col=priority&col=milestone&order=id

That report contains all tickets for this component of type defect (bug). We’ll be starting with the oldest tickets first, with the goal of seeing if we get any of these old tickets to land in 5.6.

#5-6, #bug-scrub, #upgrade-install

i18n component bug scrub for WordPress 5.6

As part of the 5.6 release, we’ll be hosting a 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. focused 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. scrub this Wednesday, September 16, 2020, 18:00 UTC in the #core channel on 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/..

They are many tickets for this component that will need feedback and help to move forward, as part of WordPress 5.6 release cycle.

During the scrub, we’ll go through these two TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. reports: https://core.trac.wordpress.org/query?component=I18N&milestone=5.6&status=!closed and https://core.trac.wordpress.org/query?component=I18N&id=39295%2C39673%2C39756%2C50040&status=!closed. These two reports contain the i18n tickets with no replies and those slated for 5.6.

#5-6, #bug-scrub, #i18n

Bug Scrub Schedule for 5.6

With 5.6 officially kicked off, time to schedule the 5.6 sessions. These ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Past Scrubs:

Upcoming Scrubs:

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

The above 5.6 scheduled 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. scrubs are separate and in addition.

For your reference, here are some of the recurring sessions:

  • Design Triage: Every Monday 16:30 UTC at #design
  • 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/ Design Triage: Every Tuesday 16:00 UTC at #design
  • 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) Scrub: Every Friday 14:00 UTC at #accessibility
  • APAC-friendly Bug Scrub: Every Tuesday at 05:00 UTC at #core will continue during the cycle, alternating focus between coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and editor.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at anytime? Yes, you can!

How? PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me (@hellofromtonya) on 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/. and let me know the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 5.6-focused? Awesome! We’ll add it to the schedule here along with your name. You’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub? All open tickets for 5.6, in order of priority, can be found here. Tickets that haven’t seen any love in a while are in particular need. Those can be found in this query.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to me (@hellofromtonya) on slack.

#5-6, #bug-scrub

WordPress 5.5.1 Bug Scrubs

The following 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. scrubs have been scheduled on tickets milestoned for 5.5.1, the conversations will take place in #core, and all are welcome to attend and take part in these meetings (requires registration).

As a refresher, here’s a post by @jorbin from the 4.7 release cycle answering questions about bug scrubs.

Reminder that the timeline for 5.5.1 will be determined after these bug scrubs and during the devchat on Wednesday, August 26, 2020 at 20:00 UTC in #core.

#5-5-1, #bug-scrub

Bug Scrub Schedule for 5.5

Now that 5.5 has been officially kicked off, 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. scrubs will happen weekly all the way up to the final release. “Early” ticketticket Created for both bug reports and feature development on the bug tracker. scrubs have already taken place. Keep an eye on this schedule – it will change often to reflect the latest information.

  1. 6/9/2020 18:00 UTC
  2. 6/18/2020 15:00 UTC
  3. 6/22/2020 23:00 UTC
  4. 7/1/2020 04:00 UTC (APAC-Friendly)
  5. 7/8/2020 21:00 UTC
  6. 7/16/2020 20:00 UTC
  7. 7/20/2020 16:00 UTC
  8. 7/27/2020 19:00 UTC
  9. 8/3/2020 TBD (If Necessary)

These scrubs are separate and in addition to the normal scrubbing and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. by individual components. Some of those sessions include:

Design Triage: Every Monday 17:30 UTC at #design
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/ Design Triage: Every Tuesday 17:00 UTC at #design
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) Scrub: Every Friday 14:00 UTC at #accessibility

The #accessibility team has also announced a set of 5.5-focused scrubs.

Also, the ongoing APAC-friendly #core bug scrub session every Tuesday at 05:00 UTC will continue during the cycle, alternating focus between coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and editor.

Finally, a reminder that anyone — Yes, you! — can host a bug scrub at anytime. You can work through any tickets you’re comfortable with. In fact, if you plan one that’s 5.5-focused, we’ll add it to the schedule here along with your name. Finally, you’ll get well deserved props in the weekly Dev Chat, as well as in the #props 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!

All open tickets for 5.5, in order of priority, can be found here. Tickets that haven’t seen any love in a while are in particular need. Those can be found in this query.

If you’d like to lead a bug scrub or have any questions or concerns about the schedule, please leave a comment or reach out to me directly.

#5-5, #bug-scrub

Bug Scrub Schedule for 5.4

Now that 5.4 has been officially kicked off, 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. scrubs will happen weekly all the way up to the final release. Keep an eye on this schedule – it will change often to reflect the latest information.

  1. 1/21/2020 19:00 UTC
  2. 1/29/2020 23:00 UTC
  3. 2/7/2020 05:00 UTC (APAC-Friendly)
  4. 2/10/2020 16:00 UTC
  5. 2/18/2020 20:00 UTC
  6. 2/27/2020 23:00 UTC
  7. 3/2/2020 18:00 UTC
  8. 3/11/2020 TBD (If Necessary)
  9. 3/17/2020 TBD (If Necessary)
  10. 3/27/2020 TBD (If Necessary)
  11. 3/30/2020 TBD (If Necessary)

These scrubs are separate and in addition to the normal scrubbing and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. by individual components. Some of those sessions include:

Design Triage: Every Monday 17:30 UTC at #design
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/ Design Triage: Every Tuesday 17:00 UTC at #design
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) Scrub: Every Friday 14:00 UTC at #accessibility

Also, the ongoing APAC-friendly #core bug scrub session every Thursday at 06:00 UTC will continue during the cycle, alternating focus between coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and editor.

Next, the Accessibility team has announced a few extra scrubs for the 5.4 cycle. You can read about those here.

Finally, a reminder that anyone — Yes, you! — can host a bug scrub at anytime. You can work through any tickets you’re comfortable with. In fact, if you plan one that’s 5.4-focused, we’ll add it to the schedule here along with your name. Finally, you’ll get well deserved props in the weekly Dev Chat, as well as in the #props 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!

All open tickets for 5.4, in order of priority, can be found here. Tickets that haven’t seen any love in a while are in particular need. Those can be found in this query.

If you’d like to lead a bug scrub or have any questions or concerns about the schedule, please leave a comment or reach out to me directly.

#5-4, #bug-scrub

WordPress 5.3.2 – bug scrubs schedule

After WordPress 5.3.1 was released, some tickets were opened to report issues with this Security and Maintenance release. Given some issues are tagged with high severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs./priority, two 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. scrubs are scheduled to address them and to evaluate the need for a potential 5.3.2 Maintenance release:

Everyone is welcome to attend these meetings on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds 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/. channel (requires registration).

#5-3-2, #bug-scrub

Twenty Twenty Bug Scrub

We will be having our first 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. scrub for Twenty Twenty on Friday, Sept 20th at 16:00 UTC, led by @ianbelanger in the #core-themes channel. All are invited to attend. Come help us scrub some bugs before the 5.3 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 release.

Reminder #1 – Monday, Sept 23rd is 5.3 Beta 1

Reminder #2 – We will be freezing commits to the github repo on Sunday, Sept 22nd 4:00 UTC to prepare for 5.3 Beta 1

As a refresher, here’s a post from the 4.7 release cycle answering questions about bug scrubs.

#5-3, #bug-scrub, #twentytwenty

Component Maintainers in 5.3

On the heels of APAC Triage and Bug Scrub Sessions and Bug Scrub Schedule for 5.3, thanks @pento and @davidbaumwald, I’d like to propose something a little bit different.

The WordPress 5.3 release is shaping up to be substantial. There are tons of fixes and improvements in 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/, for both users and developers. Even if 5.3 only included the Gutenberg update, it would have been a very nice, very desirable upgrade.

There is more to this release! Currently there are 632 tickets on the 5.3 milestone on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., both open and closed. A few smaller new features and user facing enhancements are in the works, and a lot of bugfixes and under-the-hood improvements are coming up or already done.

I’d like to propose that component maintainers take more “charge” of the tickets in their components. There is a general expectation that if you moved a ticketticket Created for both bug reports and feature development on the bug tracker. to a milestone you are the “lead” for that ticket and will see it through to completion, or move it to a future milestone if not feasible. But that shouldn’t stop component maintainers from helping to keep those tickets moving.

With the scheduled 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. scrubs, and the per-component bug scrubs that usually happen at the components’ meetings, the 329 open tickets aren’t that big of a mountain. 

The 5.3 Challenge

During the next few weeks (by 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 23 September) join me in making sure all 5.3 tickets in our components will either be resolved or moved to a future milestone. And if there are any hurdles leave a comment on the ticket briefly outlining the difficulties and include a resolution timeline.

It would also be helpful if during this time all component maintainers do a short, concise update about their component on the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chats. These updates would typically include the number of open 5.3 tickets and whether there are any difficulties with any of them. This will help people know where help is most needed, especially any newer contributors who are having trouble deciding where to spend their time.

Also, we have a Docs Wrangler for our release! After 5.3.0-beta-1 is out, it would be great if component maintainers review all changes to their component (if not already reviewed), then, if possible, help @justinahinon with writing or editing dev. notes. There are currently 301 fixes and enhancements committed to the 5.3 milestone and they will need documentation.

The proposed change for component maintainers is to act early, before beta-1, and to regularly make updates and bring any difficulties to the core dev chat.

#5-3, #bug-scrub, #components, #core

Dev Chat Summary: August 28th 2019

This post summarizes the weekly dev chat meeting from August 28th 2019 (agenda / Slack Archive).

Announcements

@chanthaboune mentioned a Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post about using SSL for auto-updates.

@francina mentioned the recently created WP-Notify working group. They had their first meeting and they have two weekly meeting so people from different timezones can attend. If you are interested, join #feature-notifications dedicated 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.

WP-Notify was also added to the features list page on Make/Core.

@francina also mentioned there is a new time slot for Core tickets/Gutenberg issues triage and bug-scrubs. If you are in the APAC timezone feel free to take part into the 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. scrubs, they are great to get started in understanding how WordPress is made.

Upcoming Releases

5.2.3

5.2.3 RC 1 is available for testing.

Release leadRelease Lead The community member ultimately responsible for the Release. @whyisjake mentioned they are skipping RC2 for 5.2.3 as there are no new commits since RC1 and no 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. was reported against RC1. The final release is scheduled for this coming Wednesday.

Please continue testing, and provide feedback. If you are new to testing Core releases, there is a guide to get started. Getting involved in testing WordPress means you will be directly involved in raising the quality of the WordPress user experience.

5.3

@francina announced that @audrasjb is joining the Release Team as focus lead for 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) part.

@davidbaumwald ran the first bug scrub of the release cycle, focused on tickets that are milestoned for 5.3, but haven’t see any movement in some time.

@johnbillion: “We need more people attending bug scrubs and scrubbing bugs. Tell all your friends.”. @davidbaumwald added that’s being added for the 5.3 cycle to give props for those running scrubs.

If you want lead a scrub, please get in touch with @davidbaumwald and it will be added to the official schedule to spread the word.

@azaozz mentioned it would also be great if component maintainers could help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. their components.

@audrasjb mentioned the accessibility team will run two additional bug scrubs dedicated to 5.3.

@karmatosed mentioned the design team also runs weekly bug scrubs.

@davidbaumwald is maintaining the list of 5.3 bug scrubs. There was a discussion about having it as a sticky post to see if it helps to increase the number of people attending bug scrubs.

@karmatosed published a post concerning the design of WP core About Page. The post is to start a discussion about what could be easier about this screen. It has a few of the current problems around it and then leads into some potential ideas. Any input on this is welcome.

Call for component maintainers

As per today, there is 6 components without maintainer. Any interested contributors is welcome to help maintain components.

@justinahinon mentioned his interest for the Site Health component.

@francina asked if all the components who seem to have a maintainer really maintained.

@jeffpaul did one component maintainers audit this year and one last year, so the current listing is nearly almost folks who committed to maintaining as best they can.

#5-2-3, #5-3, #bug-scrub, #components, #feature-plugins