Roadmap

Where Orbit is going. Dates are intentions, not promises; when this page and
reality disagree, Field Notes has the current story.

Now (0.4.x)

Polish and boring-ness: clearer plan output, faster verify polling, and
orbit doctor learning more failure signatures.

Next (0.5)

• Preview environments - every branch gets a URL
  (orbit deploy --preview), reaped automatically when the branch merges.
• Plan annotations in CI - the diff posted on the pull request, so
  reviewers see the deploy the way they see the code.

Later (0.6+)

• Multi-service plans - one plan across a set of services that must move
  together, applied in dependency order.
• Native canary analysis - error-rate comparison between releases before
  the switch commits.

Non-goals

Things Orbit will not become, so you can rely on it staying small:

• Not a CI system. Orbit runs in your CI; it will not schedule your
  builds.
• Not an observability stack. orbit logs tails releases; dashboards
  belong to tools built for them.
• Not a YAML generator with opinions. orbit.yaml stays small enough to
  read in one screen.