Twenty Twenty-One Test Scrub

As part of the 5.6 release, we’ll be hosting a Twenty Twenty-One focused test scrub today Friday, November 6, 2020, 13:30 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/..

What we will test

  1. UXUX User experience/UIUI User interface of dark-mode, in particular, https://github.com/WordPress/twentytwentyone/issues/790
  2. Bugs that need testing after WordPress 5.6 Beta 3: https://core.trac.wordpress.org/tickets/needs-testing – those marked as “Next release”

How we will test

  • We will go through each item as a group.
  • We will create a thread in Slack for each items where you can post the results. This will make it easier to reply in the existing issues or create new ones.

What do you need to test

  • WordPress 5.6 Beta 3 installed
  • To test TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. patches, you need a development environment
    • https://make.wordpress.org/core/handbook/testing/patch/
    • https://make.wordpress.org/core/2020/09/29/test-scrub-for-wordpress-5-6/#comment-39945

See you later!

#5-6, #bug-scrub, #test, #twenty-twenty-one

Twenty Twenty-One Test Scrub

As part of the 5.6 release, we’ll be hosting a Twenty Twenty-One focused test scrub today Friday, October 30, 2020, 13:30 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/..

What we will test

1. Image 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.https://github.com/WordPress/twentytwentyone/issues/737 – to test this issue, you need WP 5.6 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 + latest version (trunk) of the theme
2. Dark-mode toggle: https://github.com/WordPress/twentytwentyone-dark-mode/issues/1#issuecomment-718679339 – to test this issue, you need WP 5.6 Beta 2 + latest version (trunk) of the theme + dark mode toggle plugin
3. 2 untested blocks > Group and column https://github.com/WordPress/twentytwentyone/issues/72

How we will test

  • We will go through each item as a group.
  • We will create a thread in Slack for each items where you can post the results. This will make it easier to reply in the existing issues or create new ones.

See you later!

#5-6, #bug-scrub, #test, #twenty-twenty-one

Dev Note Scrub for WordPress 5.6

With 5.6 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 approaching fast, there will be a Dev Notedev note 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 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. 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 on 10/19/2020 19: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/..

The objectives are:

  • Recruit potential dev-note writers
  • Review tickets that need dev notesdev note 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 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.

This scrub will focus on 5.6 TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets that have the needs-dev-note keyword. Here’s the report: https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&keywords=~needs-dev-note&milestone=5.6&col=id&col=summary&col=status&col=milestone&col=keywords&col=owner&col=type&col=priority&col=component&col=changetime&order=changetime

What is a dev note?

A Developer note (or “dev note” for short) is a blogblog (versus network, site) post on the Making WordPress Core blog that details a technical change in an upcoming release and what developers need to know about that change.

Writing developer notes CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Handbook

Come join us.

This post was proofread by @hellofromtonya and reviewed by @davidbaumwald

#5-6, #bug-scrub, #dev-notes

Test scrub for WordPress 5.6

As part of the 5.6 release, we’ll be hosting test scrubs starting this Friday, October 2, 2020, 13:30 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/..

During the first meeting, we will go over the goal of the scrubs and make sure everyone is set up for testing.

During the upcoming scrubs, 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/tickets/needs-testing, addressing 5.6 tickets first.

#5-6, #bug-scrub, #test

5.6 Bug Schedule Changes for the Week of Sept 28, 2020

Please note some scheduling changes for this week.

Cancelled Scrub:

Unfortunately, today’s APAC-friendly 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, scheduled for 9/29/2020 04:00 UTC, is being cancelled.

New Scrub:

A new 5.6 ticketticket Created for both bug reports and feature development on the bug tracker. (aka bug) scrub is scheduled for 10/1/2020 17:00 UTC. Focus of this scrub will be 5.6 enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. and features that haven’t been active in awhile. Here’s the list that will be used for this scrub. It’ll happen 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/.. Come join us.

The full schedule for 5.6 scrubs can be found here.

Props to @meaganhanes for proofreading and @davidbaumwald for review.

#5-6, #bug-scrub

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 5.6 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Upcoming Scrubs:

  • 11/30/2020 TBD (If Necessary)

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

Past Scrubs:

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 Tuesday 14:00 UTC in the #design channel (for both coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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/).
  • 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 in the #accessibility channel.
  • APAC-friendly Scrub: Every Tuesday at 05:00 UTC in the #core channel. This scrub will continue during the cycle, alternating focus between core and editor.
  • Testing Scrub: Every Friday 13:30 UTC in the #core channel.

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

#core

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