Code review/commit office hours for 5.6

I will be running daily office hours for the rest of the 5.6 cycle in an effort to get more code reviewed and committed. These are to complement scheduled bug scrubs and are specifically meant to focus on reviewing and hopefully committing patches for the release cycle, not triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. or future wishlist items. My hope is that by defining specific hours people who have more structured schedules will be able to carve out that time as needed, and that other committers will be able to plan to join as much as they can.

Here are the hours I have planned, noting that in the cases where they overlap with a 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. scrub I will just stop early or start late.

• Monday-Thursday from 16:30 UTC to 18:30 UTC
• Fridays from 14:30 UTC to 16:00 UTC

Since the time shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. doesn’t seem to manage just times without a date, here is when the next 5 are in your timezone (2 hours long Monday-Thursday, 1.5 hours on Friday):

• Monday at 16:30 UTC
• Tuesday at 16:30 UTC
• Wednesday at 16:30 UTC
• Thursday at 16:30 UTC
• Friday at 14:30 UTC

I recognize that these times may not work very well for certain timezones, as I am but one person, and encourage committers in those time zones to see if there’s an opportunity there to band together and hold additional regularly scheduled code review/commit office hours.