Support new release policy #19
Labels
feature
A new functionality
Comments
3 tasks
ligurio
added a commit
to tarantool/go-tarantool
that referenced
this issue
Jun 16, 2022
Add Tarantool 2.10 [1] to testing matrix, it is a first release with datetime support. Tarantool 2.9 has been removed, it was never published [2]. setup-tarantool action does not support new Tarantool release policy [3], and Tarantool 2.10 is installed without action but using curl and apt. New issue to fix this has been submitted [4]. 1. https://www.tarantool.io/en/doc/latest/release/2.10.0/ 2. https://www.tarantool.io/en/doc/latest/release/calendar/ 3. tarantool/setup-tarantool#19 4. #186 Needed for #118
oleg-jukovec
pushed a commit
to tarantool/go-tarantool
that referenced
this issue
Jun 22, 2022
Add Tarantool 2.10 [1] to testing matrix, it is a first release with datetime support. Tarantool 2.9 has been removed, it was never published [2]. setup-tarantool action does not support new Tarantool release policy [3], and Tarantool 2.10 is installed without action but using curl and apt. New issue to fix this has been submitted [4]. 1. https://www.tarantool.io/en/doc/latest/release/2.10.0/ 2. https://www.tarantool.io/en/doc/latest/release/calendar/ 3. tarantool/setup-tarantool#19 4. #186 Needed for #118
oleg-jukovec
pushed a commit
to tarantool/go-tarantool
that referenced
this issue
Jun 23, 2022
Add Tarantool 2.10 [1] to testing matrix, it is a first release with datetime support. Tarantool 2.9 has been removed, it was never published [2]. setup-tarantool action does not support new Tarantool release policy [3], and Tarantool 2.10 is installed without action but using curl and apt. New issue to fix this has been submitted [4]. 1. https://www.tarantool.io/en/doc/latest/release/2.10.0/ 2. https://www.tarantool.io/en/doc/latest/release/calendar/ 3. tarantool/setup-tarantool#19 4. #186 Needed for #118
oleg-jukovec
pushed a commit
to tarantool/go-tarantool
that referenced
this issue
Jun 23, 2022
Add Tarantool 2.10 [1] to testing matrix, it is a first release with datetime support. Tarantool 2.9 has been removed, it was never published [2]. setup-tarantool action does not support new Tarantool release policy [3], and Tarantool 2.10 is installed without action but using curl and apt. New issue to fix this has been submitted [4]. 1. https://www.tarantool.io/en/doc/latest/release/2.10.0/ 2. https://www.tarantool.io/en/doc/latest/release/calendar/ 3. tarantool/setup-tarantool#19 4. #186 Needed for #118
oleg-jukovec
pushed a commit
to tarantool/go-tarantool
that referenced
this issue
Jun 23, 2022
Add Tarantool 2.10 [1] to testing matrix, it is a first release with datetime support. Tarantool 2.9 has been removed, it was never published [2]. setup-tarantool action does not support new Tarantool release policy [3], and Tarantool 2.10 is installed without action but using curl and apt. New issue to fix this has been submitted [4]. 1. https://www.tarantool.io/en/doc/latest/release/2.10.0/ 2. https://www.tarantool.io/en/doc/latest/release/calendar/ 3. tarantool/setup-tarantool#19 4. #186 Needed for #118
Totktonada
added a commit
that referenced
this issue
Jun 23, 2022
## 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
Totktonada
added a commit
that referenced
this issue
Jun 23, 2022
## 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
Totktonada
added a commit
that referenced
this issue
Jun 23, 2022
## 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
Totktonada
added a commit
that referenced
this issue
Jun 24, 2022
## 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
Totktonada
added a commit
to tarantool/expirationd
that referenced
this issue
Jun 24, 2022
Now the workaround for [1] is not needed, because tarantool-2.10+ releases are supported since setup-tarantool v1.3.0. The action uses the GitHub's caching infrastructure to speed up tarantool installation. [1]: tarantool/setup-tarantool#19
oleg-jukovec
pushed a commit
to tarantool/expirationd
that referenced
this issue
Jun 24, 2022
Now the workaround for [1] is not needed, because tarantool-2.10+ releases are supported since setup-tarantool v1.3.0. The action uses the GitHub's caching infrastructure to speed up tarantool installation. [1]: tarantool/setup-tarantool#19
Totktonada
added a commit
to tarantool/tuple-keydef
that referenced
this issue
Oct 3, 2022
It is easy to do now, when [1] is implemented. [1]: tarantool/setup-tarantool#19 Fixes #21
Totktonada
added a commit
to tarantool/tuple-keydef
that referenced
this issue
Oct 3, 2022
It is easy to do now, when [1] is implemented. [1]: tarantool/setup-tarantool#19 Fixes #21 (cherry picked from commit 171002d)
Totktonada
added a commit
to tarantool/tuple-keydef
that referenced
this issue
Oct 4, 2022
It is easy to do now, when [1] is implemented. [1]: tarantool/setup-tarantool#19 Fixes #21
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to the new release policy repository URL now looks like
The API of this action should be extended somehow to support the new workflow.
See also tarantool/tarantool#6182
The text was updated successfully, but these errors were encountered: