Tag Archives: bug scrub

Aaron Jorbin 4:31 am on October 3, 2016
Tags: , bug scrub   

Bug Scrubs for the week of October 3

There are a few upcoming 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 in addition to the regular component ones that you should plan on attending. Both of these scrubs will be taking place in the #core slack room.

There are only 3 weeks remaining until the first 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. for 4.7. To hit this target, there must be no remaining enhancements or feature requests. As of today, there are 72 open tickets that must be closed or punted before October 26.

Want to run a bug scrub? Learn about running your own.

#4-7, #bug-scrub

Morgan Estes 2:32 am on October 1, 2016
Tags: , bug scrub,   

Docs Bug Scrub this Weekend

Join @morganestes in the #docs channel in 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/. on Sunday, Oct. 2, 2016 3:30 p.m. CDT for a docs-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. We’ll plan for an hour of gardening fun. See you there!

#4-7, #bug-scrub, #inline-docs

Aaron Jorbin 6:09 am on September 27, 2016
Tags: , bug scrub   

Bug Scrubs This Week

There are a few upcoming 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 in addition to the regular component ones that you should plan on attending. Both of these scrubs will be taking place in the #core slack room.

Additionally, thanks to @desrosj for running a 4.7 focused scrub on Monday.

Want to run a bug scrub? Learn about running your own.

#4-7, #bug-scrub

Felix Arntz 12:23 pm on September 21, 2016
Tags: , bug scrub,   

Upcoming Multisite Bug Scrubs

After the initial 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 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 in the 4.7 release cycle last week, we will continue going through the list of bug tickets this week on Thursday 20:00 UTC, in #core-multisite as usual. The respective report was about bug tickets with the multisite focus that were opened within the last year. We have 8 tickets to go for that report, so we should be able to finish it this week.

After that, we will continue having regular multisite bug scrubs that are held every Thursday at 20:00 UTC, then focussing on multisite tickets milestoned for the 4.7 release.

If you aren’t available during the weekly multisite bug scrubs, feel free to leave a comment here or in #core-multisite if you have other tickets you’d like to see covered.

See you then!

#4-7, #bug-scrub, #multisite

Peter Wilson 2:49 am on August 30, 2016
Tags: , bug scrub   

Bug Scrub: Performance Focus

A 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 against the performance focus keyword will be taking place on Thursday, September 1, 2016 at 4pm UTC+10.

There are currently 138 tickets open against the report in various stages on the road to resolution.

Testing of tickets always smooths the road to commit so it would be dandy if you (yes you) could jump in and test some patches in advance of the scrub.

Feel free to drop some notes about tickets on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. or in the comments if you can’t make it to the scrub. It’s scheduled for an Australian friendly time. 🇦🇺

#4-7, #bug-scrub

Aaron Jorbin 8:02 pm on August 25, 2016
Tags: , bug scrub,   

Bug Scrubs for 4.7

Ensuring tickets move towards a resolution is one of the most important things we can work on as a project. Bug Scrubs serve as one of the ways to make this happen. For 4.7, I would like to invite you to run a WordPress 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. Bug Scrubs can have a general focus, focus on a specific component, or focus on a specific report (such as ancient tickets). Want to learn more? Here is a list of “Potentially Asked Questions”. Have an unanswered question? Ask it in the comments.

Continue reading →

#4-7, #bug-scrub, #core

Jeremy Felt 6:13 am on August 19, 2016
Tags: , bug scrub   

Bug Scrub for 4.6.1

The 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 4.6.1 will be Tuesday 23 August, 15:00 UTC in #core.

There are currently 9 11 tickets open on the 4.6.1 milestone in various stages of verification, patching, and testing. Working with these over the next several days before the bug scrub will help determine when a 4.6.1 release will be necessary.

Any tickets reported against trunk at this point in the cycle should also be checked for issues that may have been introduced in 4.6.

All testing is helpful, so please take a look if you have time.

See you on Tuesday!

 

#4-6-1, #bug-scrub

Dominik Schilling 5:03 pm on June 6, 2016
Tags: , bug scrub   

Bug Scrubs for 4.6 Milestone

As announced in last week’s dev chat we’ll do three 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 for the 4.6 milestone this week. These bug scrubs will only focus on tickets that are milestoned for 4.6 inclusion, in order to reduce the number of tickets open in the milestone before the enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. merge window closes on June 29th, 2016 at 20:00 UTC.

What is a bug scrub?

Scrubs are a concentrated period of time for contributors to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets while other people are around at the same time.

Dates and Times

Monday, June 6, 2016, 19:00 UTC

Led by: @chriscct7
Focus: Enhancements

Wednesday, June 8, 2016, 18:30 UTC and Wednesday, June 8, 2016, 21:00 UTC

Led by: @ocean90
Focus: Enhancements / Bugs / Progress review of tickets from previous bug scrubs

Friday, June 10, 2016, 17:00 UTC

Led by: @voldemortensen
Focus: Enhancements / Bugs / Progress review of tickets from previous bug scrubs

Goal

There are currently 78 tickets in the enhancements and features report. By the end of the week all of them should get reviewed and at least 48 should be closed (fixed, wontfixwontfix A resolution on the bug tracker (and generally common in software development) that indicates the ticket will not be addressed further. This may be used for acceptable edge cases (for bugs), or enhancements that have been rejected for core inclusion., duplicate…) or punted. That leaves 30 tickets for the next 3 weeks on which can be actively worked on.

 

Never been to a bug scrub before? Join us in the #core slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel!

#4-6, #bug-scrub

Boone Gorges 2:07 pm on May 18, 2016
Tags: bug scrub,   

Query component bug scrub – May 24

A 90-minute 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 the Query component will be held at Tuesday 24 May 2016, 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/.. We’ll spend some time looking through the Awaiting Review milestone, and we’ll have a glance at any specific tickets that attendees might interested in talking about.

#bug-scrub, #query

Adam Silverstein 2:01 am on May 17, 2016
Tags: 4.5.3, bug scrub   

Bug Scrub for 4.5.3

We will be meeting Tuesday 17 May , 20:00 UTC (at the usual coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat time) in #core to scrub bugs milestoned for 4.5.3.

There are currently 11 tickets assigned to the milestone.  Most of these have solid patches (or are already fixed and reopened for the 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".) and are tagged has-patch or commit , except #36748 which is tagged needs-patch needs-unit-tests.

Please join us to help work thru these bugs and get some patches committed!

#4-5-3, #bug-scrub