Per recent development chats, we’ve worked out a project schedule for 3.2. The scope and objectives have been set. The plan:

March 16, 2011 Confirm planned scope.
March 23, 2011 Confirm planned timeline.
April 30, 2011 Feature freeze. No new features added after this point, so that testing can begin on a stable-ish product (including usabilty testing of new features).
May 11, 2011 Target date for betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1.
UIUI User interface freeze and primary code freeze. Any last adjustments based on testing after feature freeze should be finished by now and the focus shifts to fixing bugs to get to a stable beta.
From this point on, no more commits for any new enhancements or feature requests in this release cycle (including blessed), only 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. fixes. Any enhancements/feature requests not completed and committed by this point will be punted to future.
June 1 6, 2011 Target date for RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1. String freeze; translators rejoice.
June 30ish July 4, 2011 Target date for WordPress 3.2 launch.

So: if you have made a 2011 new year’s resolution to get involved in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, now’s the time to head on over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and pick a 3.2 ticket (that sounds kind of like a carnival game, doesn’t it?). Get your patches done and submitted as soon as possible, then drum up people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. As stated above, no patches for enhancements or feature requests will be committed after the posted deadlines, so that we can all focus on squashing bugs and hopefully deliver the most bug-free WordPress to date. Wish us luck!