Skip to content

Latest commit

 

History

History
98 lines (70 loc) · 3.36 KB

RELEASES.md

File metadata and controls

98 lines (70 loc) · 3.36 KB

Releases

This document covers Vector's releases and the relevant aspect for Vector users.

  1. Channels
    1. Stable channel
    2. Nightly channel
  2. Tracking
    1. Stable channel
    2. Nightly channel
  3. Downloading
  4. Cadence
    1. Stable channel
    2. Nightly channel
  5. Guarantees
  6. FAQ
    1. Which release type should I be using?

Channels

Stable channel

The stable release channel includes official Vector releases with a semantic version.

Nightly channel

The nightly channel is released nightly, based off of the current state of the master branch. No guarantees are made with this branch. It may include experimental or breaking changes.

Tracking

Stable channel

  • Go to our Github repository and click the "watch" button in the top right. Click "Custom" and then "Releases" to only be notified for new releases. See the Github subscription docs for more info.
  • Subscribe to the Vector public calendar, release events are added.
  • Follow @vectordotdev on Twitter.
  • Head to our chat, watch the #announcements channel, and configure notifications accordingly.
  • If you are using a package manager, you should be able to see the update available when updating your package lists.

Nightly channel

Releases will appear in our nightly artifact list every night.

Downloading

Please head over to Vector's download page.

Cadence

Stable channel

  • Every 6 weeks
  • Release patch fixes as needed to fix high-priority bugs and regressions from the last major or minor release
  • Release daily builds representing the latest state of Vector for feedback

Nightly channel

  • Every night

Guarantees

Please see the versioning policy.

FAQ

Which release type should I be using?

We always appreciate early feedback on Vector as we are developing it to help ensure the highest quality releases.

If you are able to, running a nightly release of Vector allows you to test out unreleased features and fixes and provide feedback to guide our development. We aim to keep nightly as stable as possible through integration testing, but there will occasionally be issues that slip through and are fixed for the next nightly release. For example, you could choose to run the nightly version in your development environments and save stable for production. Otherwise, the stable release is your best bet.