February 18, 2010 Update: to include the new menu system, we are pushing back all dates by 2 weeks, per updated schedule below.
Per recent development chats, we’ve worked out a project schedule for 3.0. The plan:
|January 7, 2010
- Identify major features slotted for 3.0
- Begin merging MU files into trunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.
- Begin development of new default theme
- Begin development of custom post types feature
- Begin development of menu management feature
- Patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. bugs
- Work on patches for small enhancements
|January 18, 2010
- MU file merge should be complete
- Cutting edge types can start banging on the new MU integration
- Continue alpha development
|February 15 March 1, 2010
|**From this point forward, there will be no more commits for enhancements or feature requests in this release cycle, only bug 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.**
| March 22 April 2, 2010
||Begin public beta 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.
|March 29 April 16? May 1, 21, 25, 2010?
||Begin RC 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).
|April 13 May 1, 15? June 17, 2010
||Launch WordPress 3.0
So: if you have made a 2010 new year’s resolution to get involved in WordPress core 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 Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and pick a ticket Created for both bug reports and feature development on the bug tracker. (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 freeze, so that we can all focus on squashing bugs and hopefully deliver the most bug-free WordPress to date. Wish us luck!