-
Notifications
You must be signed in to change notification settings - Fork 43
[0pt] Clarify tarantool update process to a newer major version #836
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
Comments
we need to revise the entire release policy doc then: https://www.tarantool.io/en/doc/2.1/dev_guide/release_management/#release-policy |
Actually upgrading to 1.9 is not required, 1.7 -> 1.10 -> 2.1 works fine. It's quite easy to migrate using docker
|
I would add to the Max's message: using
|
The issue related to |
If we are not going to revise the entire release policy and its documentation as @lenkis mentioned above, then the estimation of the issue can be 8pt. |
Our guarantee is that Nth major version can be upgraded to (N+1)th one, but we does not guarantee the same for (N+2)th version.
Say, to update 1.7 to 2.1 we need to update it first to 1.9, then to 1.10 and only then to 2.1.
We should clarify also what is a major version of tarantool: 1.7, 1.9, 1.10, 2. The way to enumarate versions was changed since 2.*.
The text was updated successfully, but these errors were encountered: