Roadmap

Code

You should read Becoming a CKAN Developer if you plan to develop with CKAN

We use specific sprint milestones. (Usually) top milestone on trac roadmap page should be the current milestone and, as a convenience, wemay add current to the name temporarily for the duration of the milestone
Tickets should be assigned into the milestone at the start of a sprint and closed when done (in the opinion of the dev).
We should aim only to schedule tickets that are expected to get done in a given sprint (super tickets are an exception though super tickets are usually assigned to the major release milestone). If we need to move a ticket which didn't get completed to the next sprint there must be some update on progress or status including time spent so far.
An estimate of time spent on a ticket should be recorded when closing as well as a reference to the relevant closing changeset (e.g. when merged into default)
When creating tasks / tickets analysis should include an estimate time required for that task. If it is more than 2-4d you probably need to split into more than one ticket / task.

All old and only kept linked here for reference purposes.