Roadmap
The Roadmap aims to set out when certain features will appear. It reduces in clarity the further we go into the future, and is constantly being added to as we move forward.
If you're just looking to find out whether a feature is likely to end up in core or not, then take a look at the planned features page. It's just a list, but we're adding more detail to it as we go.
The wiki Roadmap has been replaced with a public trello board, to make it easier for everyone to keep track of ongoing work. If you would like to receive regular updates on our progress, you can subscribe to the Dev Blog which is updated weekly after the public developer meeting.
For information on how the new roadmap works, see visit trello.
In order to manage issue priority in GitHub, we use 3 milestones:
- Current Backlog - contains high priority issues which we really want to ship in the next release and should always have ~10 issues
- Next Backlog - contains issues which are ready to be worked on
- Future Backlog - contains issues which aren't ready to be worked on yet
The idea is that any issue in the Current or Next backlog can be picked up and worked on. If the PR gets merged, the code goes out in the next release. We ask developers to pick up issues (particularly any bugs) in the Current Backlog as a priority. The roadmap is a public guide to which features are most important for the next release, but this only covers features, not technical improvements or bug fixes.
The current general focus of the project is on shipping user-facing features, as described in the blog post Road to 0.6.
The plan is to ship as many of the user facing features as possible up until early 2015, and then switch our focus from user-facing features to 'customisation', meaning improving on the theme API, adding OAuth to the API, and getting a first version of Apps (and the dashboard) into the wild.