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

Use Tarantool version structure across the project #665

Open
DifferentialOrange opened this issue Nov 26, 2021 · 1 comment
Open

Use Tarantool version structure across the project #665

DifferentialOrange opened this issue Nov 26, 2021 · 1 comment
Labels
code health Improve code readability, simplify maintenance and so on

Comments

@DifferentialOrange
Copy link
Contributor

PR #629 introduced Tarantool version as a structure (both in module and pytest) to solve the issue of migrating to new release policy (#619). Tarantool version as a string is stored in context

TarantoolVersion string

and validated with its own regexp
tarantoolVersionRegexp = regexp.MustCompile(`\d+\.\d+\.\d+-\d+-\w+`)

We should explore the code, replace excessive regexps and parsings (if there are some) by replacing them with version as a structure.

Follows up #629 (comment)

@DifferentialOrange DifferentialOrange added the code health Improve code readability, simplify maintenance and so on label Nov 26, 2021
@DifferentialOrange
Copy link
Contributor Author

Blocked until #629 is merged

@DifferentialOrange DifferentialOrange added the blocked Not ready to be implemented label Nov 26, 2021
@DifferentialOrange DifferentialOrange removed the blocked Not ready to be implemented label Dec 28, 2021
@TarantoolBot TarantoolBot removed the teamE label Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code health Improve code readability, simplify maintenance and so on
Projects
None yet
Development

No branches or pull requests

3 participants