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 beta.
**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, UI freeze.
November 6-15, 2010 Usability testing, revisions 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 bug 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 RC; 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 core development, now’s the time to head on over to Trac 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 ticket. 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!