Version 3.0 was released on June 17, 2010.

Per recent development chats, we’ve worked out a project schedule for 3.1. The plan:

September 9, 2010 Confirm planned scope.
October 15, 2010 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).
November 1, 2010 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 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..
**From this point forward, there will be no more commits for non-blessed enhancements or feature requests in this release cycle, and these tickets will be punted to the 3.2 dev cycle.**
November 1-5, 2010 Cleanup on committed stuff by leads, UIUI User interface freeze.
November 6-15, 2010 Usability testing, revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. based on results. Additional refinements to blessed enhancements and features that are determined necessary by leads only.
November 15 23, 2010 Beta period begins; 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 3.2. No exceptions.
December 1, TBD 2010
subject to change
Begin 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).; string freeze, translators rejoice.
December 15, 2010
TBD subject to change
Launch WordPress 3.1

So: if you have made a 2010 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.1 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!