4.2 Tickets Review

To really kick off the 4.2 cycle, I thought it would be a good idea to spend an hour or two in the first week going through the ~150 tickets already in Report 6 (Next Major Releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.). I’d like to pare out any tickets that don’t yet seem feasible for 4.2 consideration and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. the ones that do.

I think it’ll give us a pretty good idea of what point we’re starting from.

The ticketticket Created for both bug reports and feature development on the bug tracker. review is set for Friday, January 23, 2015 17:00 UTC in the #core channel on Slack. Please join us.

#4-2