Roadmap — three columns, no dates

What is next, and what already happened.

This is the request board sorted by what we have committed to rather than by what is most wanted. A request moves here when it is accepted, and leaves it when it ships, naming the version it shipped in.

The current release is 0.6.0. Everything marked shipped below links to the changelog entry for the release it landed in.

The board

Three states, and what each one actually means.

Planned 0

Accepted and on the roadmap. Not started, and not dated.

Nothing is queued at the moment. What gets planned next comes off the request board.

In progress 0

Being built now. It will name its release when it ships.

Nothing is mid-build right now. When something is, it appears here before it ships.

Shipped 0

Released. The version is on the request and links to its changelog entry.

Nothing filed on the board has shipped yet. The changelog records everything that has.

How things get here

A request becomes a plan, or it gets a reason.

Votes are the loudest input into what gets built next, and they are not the only one. A request also has to be safe to build, possible to roll back, and worth the maintenance it will cost forever.

A request with three votes can ship before one with forty, if the three are the same problem seen from three angles and the forty are a feature that would need arbitrary code execution to implement.

Nothing here is a commitment or a date. When something is accepted it moves to Planned, and when it ships the request names the release it shipped in.

Go to the request board File a request

What is deliberately not on this page

Dates. There are none, and there will not be. A date on a roadmap is a promise made by someone who does not yet know what the work involves.
A private list. There is no roadmap behind this one. What is here is what there is.
Anything unreleased to try. There is no beta and no early-access build. The public release and the public main branch are the two versions that exist.

The declined requests are on the board, with the reason written on each one. That list is worth reading before filing something — it is the clearest statement of what SiteHelm is not going to be.