The road to 1.0 #1538
Description
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.
When will Vector reach 1.0?
We are targeting Q2 of 2021.
What does 1.0 mean to us?
- 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.
What does pre-1.0 mean to us?
- 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.
What about post 1.0?
We will be focusing heavily on end-to-end use cases and going deeper on verticals such as:
- Best-in-class Kubernetes observability.
- Application observability.
- Infrastructure monitoring.
- Security & compliance.
- Improved parsing & structuring.
- Enterprise reliability & guarantees.
- Fleet wide management.