Bug Scrubs for 4.6 Milestone

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

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

Welcome!

Communication

What is a bug scrub?

Dates and Times

Goal

Share this: