What happens to your post

The six statuses, what each one means, and what moves a post between them.

Written By Dustin

Last updated 26 minutes ago

Every post is read by a person. New posts and comments are held for review before they appear — moderation stays on until general availability, because it is the only thing that stops an accidentally posted vulnerability or a pasted repository file from becoming public.

The six statuses

Under reviewThe default. It has been seen, not yet decided.
Needs infoWe asked you a question and cannot proceed until you answer.
PlannedDecided, and an engineering ticket is opened by hand. No date attaches to this.
In progressSomeone is actively working on it.
ShippedIt is released, and the release notes say so.
Not plannedDecided against, with a written reason.

Those six are the whole set, in that order. There is no "acknowledged", no "backlog", and deliberately no status meaning "merged but not released".

What moves a post

A post sitting in Under review gets one of three things: a status, a merge into the duplicate it belongs with, or one clarifying question — which also sets Needs info.

A post in Needs info with no reply eventually becomes Not planned. That is not a judgement on the idea; it is only that we cannot act on it. Reply and it reopens.

Planned means the decision is made and an engineering ticket has been opened by hand. In progress is then set from that ticket, so it reflects real work rather than intent. If the ticket is cancelled, the post moves to Not planned automatically and the written reason is added on the board afterwards — the automatic move sets the status, never the explanation.

There is deliberately no automatic Shipped. Merged is not released, so only a release sets it, by hand, one post at a time.

The whole chain

  1. You post. It is held for moderation, then approved.
  2. Triage gives it a status, a merge, or one question.
  3. On Planned, an engineering ticket is opened by hand carrying a paraphrased title and a link back to your post. The body of your post is not copied into it.
  4. Work starts and the post moves to In progress.
  5. The change lands and the release notes are written before anything is announced.
  6. The documentation deploys, the post is set Shipped, and you are notified with a link to the release-notes entry.

What you will not get

A date. TOVIO is pre-release and publishes no response times and no delivery estimates — on a post, on the roadmap, or anywhere else. What you will get is one more notification, when it ships.