-
Notifications
You must be signed in to change notification settings - Fork 752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Databend release channels #2559
Labels
C-documentation
Category: documentation
Comments
Recorded at https://databend.rs/doc/releases/release-channels, closing now. |
ping @BohuTANG, I think it's better to refer to our docs instead of an ongoing issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi All!
What's Databend release channels?
Databend release process following the 'release train' model used by e.g. Rust, Firefox and Chrome, as well as 'feature staging'.
But in the early stage Databend will upgrade the nightly version number only, and when a nightly version is ready for beta, we will leave a beta version getting off of the nightly version.
Ok, Let's start by understanding how Databend do the releases.
The following is mainly from the Rust documentation How Rust is Made and “Nightly Rust”.
There are three release channels for Databend(this is same as Rust):
So as time passes, our releases look like this, once a night:
Every six weeks, it’s time to prepare a new release! The beta branch of the Databend repository branches off from the main branch used by nightly. Now, there are two releases:
Six weeks after the first beta was created, it’s time for a stable release! The stable branch is produced from the beta branch:
This is called the “train model” because every six weeks, a release “leaves the station”, but still has to take a journey through the beta channel before it arrives as a stable release.
Notes
Roadmap 2021
https://databend.rs
The text was updated successfully, but these errors were encountered: