The road to 1.0 - Githubissues

binarylogic commented 4 years ago

As Vector approaches 1.0, we want to be as transparent as possible with our development and planning efforts.

Vector's 1.0 Roadmap

Vector's roadmap is public: https://roadmap.vector.dev

Each card on the roadmap represents a 1.0 feature.
Cards are not sorted in any particular order.
We bucket individual Vector issues within each epic via Zenhub.
You can see which issues we're working on via our milestones, which represent sprints with a 2-week cadence.
Everyone is encouraged to propose new issues or comment on existing ones.

We are targeting Q2 of 2021.

A stable API. As defined by semantic versioning. This includes any user-facing part of Vector: the CLI, configuration schema, and everything exposed through Vector's components.
Production readiness. High confidence that Vector will perform well in large demanding production environments. You can read more about he we define "production readiness" here.
Achieves Vector's vision. A high-performance, vendor-neutral tool that collects all observability data and gets it to its destination.

Possible API changes. Although, we do not take this lightly and will try to bundle breaking changes into a single release to reduce the migration burden.
Possible roadmap changes. We work closely with many Vector users and learn a lot in that process. These findings are likely to alter the 1.0 roadmap.

We will be focusing heavily on end-to-end use cases and going deeper on verticals such as:

jadbaz commented 1 year ago

Hello, The last milestone on the roadmap linked above is in May 2022 So this seems to be outdated Any other updated documentation on 1.0 roadmap?

pront commented 1 week ago

Hello, for anyone interested we still want to hit v1 but that won't happen until at least H2 2025.