How Vector uses issues

[binarylogic]

Vector uses Github Issues for both bug and feature tracking. This is why the Vector repo has so many issues.

Filing Issues

We use Github issues templates to guide you. Simply choose the appropriate issue type and fill out the issue accordingly.

Chat with us

You can join the Vector chat and chat with us directly.

Looking for easy first issues?

Check out Vector's contribute page.

Help Build Our Roadmap

Just add a 👍 reaction to the issue. The Vector team regularly evaluates issues sorted by the most 👍 to inform our roadmap.

[tshepang]

link to roadmap is broken

[jszwedko]

link to roadmap is broken

Thanks @tshepang . I dropped the roadmap link since that doesn't exist anymore, as you noted. I am hoping we can republish a public roadmap soon though, at which point I'll re-add it.

[JacksonSc]

Is there any update on the roadmap and when version 1.0.0 will be available?

[jszwedko]

Is there any update on the roadmap and when version 1.0.0 will be available?

Not yet, but is there something in particular about a 1.0.0 version that would be important to you? Is it backwards compatibility guarantees? Or something else? The context would be helpful to us.

[JacksonSc]

It's about breaking changes during pre-1.0 versions and keeping our vector installations (dozen's of them) up-to-date. Currently the minor versions contain breaking changes which are well documented. It would simply the rollout of minor / patch version if there are no breaking changes included.

[tshepang]

an ideal case is migration tooling with each release, which would maybe help people keep updated