feature: support 2.10+ releases #24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Background
The new release policy (see [1]) is in effect since Tarantool 2.10 and
changes several things, including:
1. Repositories layout.
- The new release series naming: `series-2` instead of `2.10`, `2.11`
and so on.
- The new `pre-release` repository.
- No nightly builds (`live` repository).
2. Versioning.
- Three digit versions for release builds: `2.10.0` instead of
`2.10.0.0`.
- `alpha`, `beta`, `rc` marks in pre-release tarantool versions.
[1]: tarantool/tarantool#6182
## Usage
This commit offers support of 2.10+ *releases* and leaves pre-releases
unsupported (it is tracked in #23).
The usage is quite straightforward:
```yaml
steps:
- uses: actions/checkout@v2
- uses: tarantool/setup-tarantool@v1
with:
tarantool-version: '2.10.0' # or '2.10', or just '2'
```
The latest 2.10.X version will be installed for
`tarantool-version: '2.10'`. The latest 2.X.Y version will be
installed for `tarantool-version: '2'`.
## Implementatoin details
We have nothing to do regarding versioning in order to support 2.10+
*releases*. However we should reflect the repository layout change:
* tarantool-version: 2.8, nightly-build: false or unset
(Nothing is changed here.)
```
baseUrl: https://download.tarantool.org/tarantool/release/2.8
```
* tarantool-version: 2.8, nightly-build: true
(Nothing is changed here.)
```
baseUrl: https://download.tarantool.org/tarantool/2.8
```
* tarantool-version: 2.10, nightly-build: false or unset
(This is the new logic introduced by this commit.)
```
baseUrl: https://download.tarantool.org/tarantool/release/series-2
```
* tarantool-version: 2.10, nightly-build: true
(This is the new logic introduced by this commit.)
Raise an error.
If the version is set as `'2'` or `'2.10.0'`, use the same logic as for
`'2.10'`.
Fixes #19
|
Tested on the smtp module: tarantool/smtp@e0f1504. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
The new release policy (see tarantool/tarantool#6182) is in effect since Tarantool 2.10 and changes several things, including:
series-2instead of2.10,2.11and so on.pre-releaserepository.liverepository).2.10.0instead of2.10.0.0.alpha,beta,rcmarks in pre-release tarantool versions.Usage
This commit offers support of 2.10+ releases and leaves pre-releases unsupported (it is tracked in #23).
The usage is quite straightforward:
The latest 2.10.X version will be installed for
tarantool-version: '2.10'. The latest 2.X.Y version will be installed fortarantool-version: '2'.See notes on the implementatoin details in the commit message.
Fixes #19