Wednesday was the Weekly WordPress Developer Chat and this week the core team talked over what will be the theme for the WordPress 3.4 development cycle. As pointed out by Jane Wells, while WordPress 3.3 had a lot of features it wasn’t centered around a specific theme. With 3.4 the team will return to having a theme for each release.
In an agile development cycle like the core team is trying to adapt, it’s a really good idea to have a theme to center the release around. It really helps focus the efforts of features and bug reporting, so you’re touching similar files and not jumping all over the place.
As proposed at the core team’s meetup in Tybee, the team is going to try something new. Wells said:
At Tybee meetup, I proposed we experiment with our process to try and overcome some of our historical downfalls (lack of good time estimation, resource bottlenecks, lack of accountability, unknown/variable time commitments/disappearing devs, overassignment of tasks to some people, reluctance to cut features to meet deadline), and the core team worked as a group to come to the following process proposal.
They are going to focus on a few areas from a development cycle side of things: Schedule, Time Commitment, Time Tracking, Scope [creep], and Choosing Teams.
If you could add anything to WordPress in the next release, what would you add?