The plan:

July 27, 2013 WordPress 3.7 announced.
July 28, 2013 Kick-off at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. San Francisco Hack Day.
August 7, 2013 Initial meeting to scope out the release. See this post and this one.
Week of Sept. 16, 2013
September 28, 2013
Beta 1. At this point, development of new initiatives (updates, language packs, etc.) should be complete.
From this point on, no more commits for any new enhancements or feature requests in this release cycle, 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 and inline documentation. Any enhancements/feature requests not completed and committed by this point can be resumed in just a few weeks at the start of WordPress 3.8.
October 10, 2013 Beta 2.
Week of Sept. 30, 2013
October 18, 2013
Release candidaterelease 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.
Week of Oct. 14, 2013 Week of Oct. 21, 2013 Target date for release of WordPress 3.7.

To get involved in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, 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.7 ticket. Need help? Check out the Core Contributor Handbook.

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!