Skip to content
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

Support new version policy #27

Open
DifferentialOrange opened this issue Aug 9, 2022 · 0 comments
Open

Support new version policy #27

DifferentialOrange opened this issue Aug 9, 2022 · 0 comments

Comments

@DifferentialOrange
Copy link

DifferentialOrange commented Aug 9, 2022

Since 2.10, Tarantool have a new release policy: https://www.tarantool.io/en/doc/latest/release/policy/

For example, versions like 2.10.0-beta1 is possible now. Versions with -alphaN, -betaN, -rcN and -entrypoint suffixes are prior to non-suffixed one. It is possible that 2.10.0-beta1 will not have all features that supported by 2.10.0. But now version restrictions in code and tests do not support new release policies.

Also it may be needed to rework approach to extracting a version for a connection. For example, when box.info.version and _TARANTOOL is 2.10.0-beta2-91-g08c9b4963-r472, greeting returns Tarantool 2.10.0 (Binary) string.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant