The following schedule is subject to adjustment, but reflects the current thoughts on achievable milestones.
| January 02-09, 2013 | Confirm proposed scope and secure team leads. |
| January 09, 2013 | Development begins. |
| April 04, 2013 | Hard freeze on feature development. Stop feature development; focus on testing and compatibility (supported platforms, browsers, RTL, accessibility, etc). Ship a Beta 1. |
| From this point on, no more new feature requests in this release cycle, only fixes for issues in current features. | |
| April 29, 2013 | Beta 2 |
| May 03, 2013 | Beta 3 |
| Release Candidate 1 target date. String freeze. Any work is focused on regressions and blockers only. | |
| Release Candidate 2 | |
| Target date for WordPress 3.6 launch. | |
To get involved in WordPress core development, head on over to Trac and pick a 3.6 ticket. Need help? Check out the Core Contributor Handbook.
Shashank Shekhar 10:45 pm on January 14, 2013 Permalink | Log in to Reply
If really menu is going to be enhanced in wp 3.6, it should include capability to include widgets in menu items. Also sould be possible to put some html inside menu. To overall effect to be generate megamenu structure with easy gui. Menu icons, and subtitle with each menu should also be possible. For ex. see menu/submenu on http://wpmegamenu.com/
Marius84 12:12 am on January 20, 2013 Permalink | Log in to Reply
i can’t wait for the next relase!
hovida 12:04 pm on January 25, 2013 Permalink | Log in to Reply
Wow, Great – 3.6 begins! I will perform many functions to make WP faster. i hope i can fix many slow functions