I cleared out all tickets in Awaiting Review…

I cleared out all tickets in Awaiting Review with a reported version of 3.3. They would normally show up at the top of report 40.

If anyone wants to help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. the next group — “Defects Awaiting Review, reported against no version” (59 tickets) — here’s some ways to triage a ticketticket Created for both bug reports and feature development on the bug tracker.:
— If it’s an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. or feature requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged., change the ticket type.
— If it’s 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. that effects a previously released version of WordPress, then change the version field.
— If there isn’t enough information in the ticket, ask the reporter for more information and add the “reporter-feedback” keyword.

The main goal here is to identify regressions from 3.2 to 3.3, i.e., things that broke during this development cycle. We typically do a sweep each release not long before RC1, to make sure we didn’t miss a bad bug that was already reported.