Description
I propose to introduce the following aliases for numeric tarantool versions for the tarantool-version field and update them in sync with our release cycle.
(Release series and releases are pointed just for example. They are actual at the moment of writting, 2020-12-24, but may be not actual at the time of reading this issue.)
| Alias | Release series | Release |
|---|---|---|
alpha |
2.7 | 2.7.0 |
beta |
2.6 | 2.6.1 |
stable |
2.5 | 2.5.2 |
oldstable |
2.4 | 2.4.3 |
lts |
1.10 | 1.10.8 |
latest |
? | ? |
I don't know, whether it would be better to point latest to stable, beta or even alpha. It is subject to discuss.
Those aliases are convenient, when one want to verify a module (a connector, a tool) against all actual tarantool versions and don't bother with updating the numeric versions every quarter. I think the feature would be useful as for per-push testing (to verify changes in the module) as well as for nightly testing (to verify the module against changes in tarantool).