Bug scrub schedule for WordPress 6.5

This post lists 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 sessions dedicated to move things forward towards the next major WordPress release, 6.5, slated for March 26, 2024.

The full 6.5 Release Schedule.

Everyone is welcome to join to help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets, explore tickets to contribute to by creating patches, writing or conducting tests, providing code reviews, and more. Things to keep in mind:

  • all features and enhancements should be in the 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. before 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 (February 13, 2024) and most bugs and all strings need to be there before 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 (RC1)
  • If you are working on a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., it is helpful if you can please plan your contribution to give enough time for other contributors to make suggestions, review and test.

Alpha Bug Scrubs

Focus: general triage

Focus: features, enhancements and then bugs

Beta Bug Scrubs

Focus: rest of the bugs plus reported regressions

  • Dates will be added as the development cycle progresses

Release Candidate Bug Scrubs (if needed)

Focus: issues reported from the previous Release Candidates.

  • Dates will be added as the development cycle progresses

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

Regular component scrubs and triage sessions

Below is a list of some of the recurring sessions which take place in the Make WordPress Slack.

Have a regular component scrub or triage session?
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.” @audrasjb@chaion07, @rajinsharwar on Slack to have it added to this page.

Start your own triage sessions

Decide what you want to focus on first.

The 6.5 triage sessions and moving forward these tickets are the priority for the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team and the release. If you would like to lead sessions for these, they can be arranged and added to this schedule.

However, if you are interested in particular component or user focus, for example, to take care about RTL-tickets, this will be very welcome too.

Could you run a session to scrub old tickets? There are treasures which would benefit from scrubs and more contributors working on them in older tickets.

How to help?

  • In the core channel on Slack, ping @audrasjb, @chaion07, @rajinsharwar or one of the core team reps on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Useful reports and information

  • More will be added as the development cycle progresses

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

#6-5, #bug-scrub, #core, #props

Bug Scrub Schedule for WordPress 6.4

Following sessions are dedicated to move things forward and be ready in time according to 6.4 Release Schedule.

Everyone is welcome to join not only to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets but also to look for tickets you can contribute by creating patches, making code review and testing. Keep in mind that all features and enhancements should be in the 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. before 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 and most bugs and all strings need to be there before RC1. If you are working on a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., plan your contribution to have enough time for other contributors to make suggestions, review and test.

Alpha Bug Scrubs

Focus: features, enhancements and then bugs

Beta Bug Scrubs

Focus: rest of the bugs plus reported regressions

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). Bug Scrubs (if needed)

Focus: issues reported from the previous RC.

  • TBD

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

Regular component scrubs and triage sessions

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

Have a regular component scrub or triage session?
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.” @audrasjb@oglekler or @marybaum 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/. to have it added to this page.

You can start your own triage sessions

  • Decide what you want to work on

6.4 triage session are our priority and moving forward tickets which already are scheduled for the release is most needed task. If you want to lead some of them, they can be added on this schedule.

But if you are interested in particular component or user focus, for example to take care about RTL-tickets, this will be most welcome too.

Especially interested can be the session to scrub old tickets. We are continuously closing new tickets with the same topic in favor of existing ones and because these tickets are looking complicated just because they’re age not, so many contributors are eager to work on them, but there are actual treasures hidden among very difficult or tricky topics.

  • Ping @oglekler or @marybaum on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Useful reports and information

  • Report 5 provides a list of all open 6.4 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 6.4 tickets ordered by workflow.

Need a refresher on 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? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Thanks to @audrasjb, @mukesh27 and @marybaum for helping to put together this agenda and peer review.

#6-4, #bug-scrub, #core, #props

New in 6.3: Rollback for failed manual plugin and theme updates

Should the manual 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 or theme update process fail, the rollback feature will automatically restore the previously installed version to ensure the website remains available to its users.

The Rollback feature originated in #51857.

When updating a plugin or theme, the old version of the plugin or theme is moved to a wp-content/upgrade-temp-backup/plugins/PLUGINNAME or wp-content/upgrade-temp-backup/themes/THEMENAME folder.

The reason we chose to move instead of zip, is because zipping/unzipping are resources-intensive processes, and could increase the risk of failure on low-end, shared hosts. Moving files, on the other hand, is performed instantly and won’t be a bottleneck.

Moving is accomplished by means of the new move_dir() function, included in WordPress 6.2. PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher’s rename() is used for this with a fallback to copy_dir(), a recursive file copy used by CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for a long time. move_dir()uses the ::move()method for the WP_Filesystem_DirectWP_Filesystem_FTPextWP_Filesystem_ftpsockets, and WP_Filesystem_SSH2 filesystem abstractions and has a fallback to copy_dir(). Find out more in the move_dir() devnote.

If the update process fails, then the backup we moved in the “upgrade-temp-backup” folder is restored to its original location. If the update succeeds, then the backup is deleted.

Two new checks were added in the Site Health screen:

  • Check to make sure that the backup folders are writable.
  • Check there is enough disk-space available to safely perform updates.

To avoid confusion: The “upgrade-temp-backup” folder will NOT be used to “roll back” a plugin/them to a previous version after a successful update. You can use the various rollback plugins for this.

The “upgrade-temp-backup” folder will simply contain a transient backup of the previously installed plugin or theme getting updated, and as soon as the update process finishes, the folder will be emptied.

When a rollback occurs, the user should simply see that there is an update pending and their site should still be working.

The simplest explanation of what results in a manual update failure and a rollback is anything that returns a WP_Error from WP_Upgrader::install_package().

  1. A bad request, something missing the source or destination of the update.
  2. WP_Error returned from the upgrader_pre_installupgrader_source_selectionupgrader_clear_destinationupgrader_post_install filters.
  3. An empty download package.
  4. A failure when moving the moving the installed plugin/theme to the temp-backup directory.
  5. If the remote source destination folder not able to be cleared and something is there.
  6. Unable to create remote destination folder.
  7. Unable to move/copy the the update to the remote destination.

Updated August 2, 2023 @afragen

The above encompasses parts 1 and 2 of the Rollback feature. Part 3, hopefully for WordPress 6.4, is the same process but for automatic updates. Specifically, Rollback part 3 checks to see that the updated plugin does not cause a PHP fatal error when activated. If it does, this error is captured and the previously installed version is restored.

All of the Rollback feature, parts 1-3, are included for testing in the Rollback Update Failure feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins..

Props @costdev for peer review, @stevenlinx and @desrosj for review.

#6-3, #dev-notes, #dev-notes6-3, #props

Bug Scrub Schedule for WordPress 6.3

It’s time to schedule the 6.3 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 sessions!
These 6.3 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Bug Scrubs

Beta Bug Scrubs
Focus: issues reported from the previous beta.

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). Bug Scrubs (if needed)
Focus: issues reported from the previous 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)..

  • TBD

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?

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

Have a recurring component scrub or triage session?
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.” @audrasjb, @chaion07, @oglekler, or @mukesh27 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/. to have it added to this page.

Want to lead a bug scrub?

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

How? Ping @audrasjb, @chaion07, @oglekler, or @mukesh27 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 6.3-focused? Awesome! It can be added it to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 6.3 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 6.3 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Thanks to @chaion07, @oglekler, or @mukesh27 for helping to put together the agenda.

#6-3, #bug-scrub, #core

Bug Scrub Schedule for 6.2

With 6.2 well underway, it’s time to schedule the 6.2 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 sessions. These 6.2 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Bug Scrubs

Hosted by @costdev

Hosted by @mukesh27 (APAC-Friendly)

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. Bug Scrubs
Focus: issues reported from the previous beta.

Hosted by @costdev

Hosted by @mukesh27 (APAC-friendly)

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). Bug Scrubs (if needed)
Focus: issues reported from the previous 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)..

Hosted by @costdev

Hosted by @mukesh27 (APAC-Friendly)

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?

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

Have a recurring component scrub or triage session?
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.” @costdev or @mukesh27 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/. to have it added to this page.

Want to lead a bug scrub?

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

How? Ping @costdev or @mukesh27 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 6.2-focused? Awesome! It can be added it to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 6.2 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 6.2 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @costdev or @mukesh27 on Slack.

Props to @hellofromtonya for reviewing the post.

#6-2, #bug-scrub, #core

Early Bug Scrub Schedule for 6.1

As work begins on 6.1, it’s time to schedule some early 6.1 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 sessions.

These scrubs will happen once a week, usually scheduled for Thursdays at 18:00 UTC, though there may be some adjustments to accommodate releases, as well as religious and national holidays.

Right now, this only includes Early Scrubs. A release schedule for Alpha, 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., and 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). scrubs will follow soon.

Early Scrubs:

Focus: early tickets milestoned for 6.1, tickets that require more time or early testing.

Hosted by @costdev

Hosted by @audrasjb

Starting from Thursday, 23 June 2022, 20:00 UTC, @audrasjb will be hosting recurring 6.1 bug scrubs every Thursday at 20:00 UTC.

Hosted by @chaion07

Starting from Tuesday, 7 June 2022, 05:00 UTC, @chaion07 will be hosting recurring 6.1 bug scrubs every Tuesday at 05:00 UTC.

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?

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

Have a recurring component scrub or triage session?
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.” @costdev 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/. to have it added to this page.

Want to lead an Early Bug Scrub?

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

How? Ping @costdev on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Your scrub can be added it to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @costdev on Slack.

Props to: @hellofromtonya for proof-reading.

#bug-scrub, #core

Bug Scrub Schedule for 6.0

With 6.0 well underway, it’s time to schedule the 6.0 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 sessions. These 6.0 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Bug Scrubs

Hosted by @costdev

Hosted by @chaion07 (APAC-Friendly)

Hosted by @mikeschroder (APAC-Friendly)

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. Bug Scrubs
Focus: issues reported from the previous beta.

Hosted by @costdev

Hosted by @chaion07 (APAC-friendly)

Hosted by @mikeschroder (APAC-Friendly)

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). Bug Scrubs (if needed)
Focus: issues reported from the previous 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)..

Hosted by @costdev

Hosted by @chaion07 (APAC-Friendly)

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?

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

Have a recurring component scrub or triage session?
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.” @costdev or @chaion07 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/. to have it added to this page.

Want to lead a bug scrub?

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

How? Ping @costdev or @chaion07 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 6.0-focused? Awesome! It can be added it to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 6.0 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 6.0 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @costdev or @chaion07 on Slack.

Props to: @davidbaumwald for proof-reading.

#6-0, #accessibility, #bug-scrub, #core, #core-test

Dev Chat Summary Dec 16th 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, December 16, 2020, 05:00 UTC, and Wednesday, December 16, 2020, 20:00 UTC. Both chats followed this agenda.

05:00 UTC core dev chat
@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@laurora facilitated the meeting and @thelmachido took notes. Find the full Slack archive here.

Announcements

Reminder – State of the Word is today. Set your alarm for the time Thursday, Dec 17th, 2020 at 1600 UTC so you don’t miss it!!

The 5.6 retrospective has started! We’d love as many of you as possible to share your feedback with us via the form linked in this post

The Full Site Editing Outreach program is officially underway. It will start with the release 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/ 9.6 around December 23rd with plenty of time to be involved. If interested in joining the fun, please head on over to #fse-outreach-experiment. There is a comprehensive status update on Site Editing, view the post from Matias.

@abhanonstopnewsuk would like to inform us that the questions and answers on the release have had some updates thanks to a number of comments from user experience, to further help non-technical users. These updates will be posted on 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/.

Highlighted Posts

Component maintainers and focus leads

Build/Test Tools
Work has continued on GitHub Actions in this ticketticket Created for both bug reports and feature development on the bug tracker. #50401. There are also 3 relevant commits to take note of. r49781 Disable GitHub Action workflow runs triggered on push for forks and mirrors. r49782  Use NodeJS 14 in GitHub Action workflows. r49783  Enable reporting of results to WordPress.org

Site Health
A small ticket for 5.6.1 came in today, so it’s looking manageable

@clorith pointed out that jQuery updates got flagged early

Comments Component
@imath updated the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. on this ticket #33717, feedbacks welcome

@flixos90 is planning to commit iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. lazy-loading today #50756

Upgrade and Install
There is a plan to have error stats for 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/theme updates failures sent to dotorg #51928 in 5.7

Open Floor

  • @iandunn would like to get some broader feedback on #51966 – please review and leave comments on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
  • A question was raised during chat, does a theme upgrade require being tied to a core upgrade?. The issue was raised because of this ticket #52040 @audrasjb said that this issue can be fixed in a TT1 release because a theme upgrade doesn’t need to be tied to a core upgrade. You can follow the full conversation here.
  • Learn WordPress was launched yesterday and a big cross teams effort including contributors from community, training, marketing, polyglots, design, metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., core and more. There are some more fun promotions in store too. Social videos have been produced for the promotion of Learn WordPress. Here is an example, the team would like to encourage contributions in other languages.  They’re also exploring how to support older audiences to use WordPress through the resources on Learn WordPress. Any hands to help with this? 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.” @nalini 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/..
  • @annezazu worked to redo the core feature projects page. Project owners where contacted for the latest status, description/intro paragraphs where updated, core editor items where added, and inactive projects where hidden to make the page more focused.

Next Dev Chat Meeting

The next meetings will take place on Wednesday, December 23rd 2020, 05:00 UTC and Wednesday, December 23rd 2020, 20:00UTC in the #core Slack 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 this post so that we can take them into account. 

#props to @thelmachido for consolidating both sets of notes together prior to publishing.

#5-7, #summary

Dev Chat Agenda: 25th November 2020

Here is the #agenda for this week’s #dev-chat meetings happening at:
Wednesday, 25th November 2020, 0500UTC and Wednesday, 25th November 2020, 2000UTC.

  • Announcements
  • Highlighted blogblog (versus network, site) posts –
    • A Week in Core – November 23, 2020 – Get all the news here.
    • Discussion: align the WordPress release cycle with the industry standard – Please add your thoughts.
    • WordPress 5.7: What’s on your wishlist? – Please add your thoughts.
    • WP 5.6 Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.WordPress 5.6 Field Guide – Make WordPress Core
    • 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, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. continue to be updated ready for final release, here’s the latest dev-notes – Make WordPress Core
  • Calls from component maintainers and/or focus leads
  • Open Floor
    If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday, 25 November 2020, 05:00UTC and Wednesday, 25 November 2020, 2000UTC. These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#props to @peterwilsoncc for review

#5-6, #agenda

Howdy 3.2 contributors The new credits page in…

Howdy 3.2 contributors: The new credits page in 3.2 (#17384) now pulls your name from your WP.org profile. So if you want your full name to show up, go update it.

Mine is here. When you’re logged in, the Edit link on your own profile and the subsequent name field are both rather obvious.

Potential contributors: This enough incentive to contribute to 3.2? 🙂 Go grab the beta.

(Fine print: Server cache updates every 12 hours. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. cache updates once a week, so you’ll need to flush the transient to see it on your own install.)

#profiles, #props