The WordPress.org support forums were taken offline this morning to help resolve data corruption and uptime issues with a database cluster, which had caused intermittent downtime across the WordPress.org network. All problems have been resolved and the support forums have been brought back online.

You can follow a new status.wordpress.org blog (hosted elsewhere, on WordPress.com) for future status messages. (You can subscribe to that site via email.)

What about tickets assigned to Awaiting Review milestone? At first I thought it was a good idea, but now it looks like Future Release milestone (846 tickets in AR milestone, 1686 in FR). It will be good to quickly review all these tickets and decide which ones can go to 3.3. In 3.4 we either need to conduct a weekly scrub meetings to review all new tickets, or completely get rid of this milestone and let everyone edit the milestone field (or assign next major release by default if you do not want to let anyone to edit it).

Then the issue becomes us punting everything to Future when we’re ready to go to beta, and they further rot. It’s a mess. Locking down the milestones did help. It keeps scope manageable, allows trusted core contributors to make decisions. There are a number of non-committers who have access to these fields.

Yes, sometimes, some tickets fall through. There will always be bugs. But certainly not many get flat-out missed.

You’re right, both buckets need a serious cleaning. We should probably do this systematically after we hit RC and branch 3.3 off. Then trunk can become early development and we can scrub in the month of December.

If anyone sees anything in Awaiting Review now that needs 3.3 attention (non-enhancements), feel free to leave a comment to that effect, and someone will promote it.