# Best practices for testing on LTS and latest release (Travis, ...)
**URL:** https://discourse.julialang.org/t/best-practices-for-testing-on-lts-and-latest-release-travis/46250
**Category:** Tooling
**Tags:** question
**Created:** [September 8, 2020, 8:56am UTC](https://discourse.julialang.org/t/best-practices-for-testing-on-lts-and-latest-release-travis/46250 "2020-09-08T08:56:20Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [September 8, 2020, 8:56am UTC](https://discourse.julialang.org/t/best-practices-for-testing-on-lts-and-latest-release-travis/46250/1 "2020-09-08T08:56:20Z")
Whenever a new minor version of Julia is released, I just add that version to my `.travis.yml`. I recently realized that this leads to a lot of testing on versions that are no longer supported.
Is there a way to test on the **LTS** and the **latest minor version** automatically, without manual intervention? I am aware that I can do
```yaml
language: julia
julia:
- 1.0
- 1
```
which will currently give me 1.0.5 and 1.5.1, but that still requires specifying the LTS manually.
---
### Author:  [@ctkelley](https://discourse.julialang.org/u/ctkelley)
#### Post date: [September 8, 2020, 10:51am UTC](https://discourse.julialang.org/t/best-practices-for-testing-on-lts-and-latest-release-travis/46250/2 "2020-09-08T10:51:29Z")
If not travis, can github actions do this?
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [September 8, 2020, 11:52am UTC](https://discourse.julialang.org/t/best-practices-for-testing-on-lts-and-latest-release-travis/46250/3 "2020-09-08T11:52:04Z")
I think a version specifier like `1-lts` could make sense.
@ararslan @staticfloat @StefanKarpinski, what do you think?
---
### Author:  [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)
#### Post date: [September 9, 2020, 7:54am UTC](https://discourse.julialang.org/t/best-practices-for-testing-on-lts-and-latest-release-travis/46250/4 "2020-09-09T07:54:15Z")
I think once upon a time we talked about adding an “LTS” alias to the `setup-Julia` GitHub Action.
@SaschaMann @davidanthoff What did we decide?
---
### Author:  [@SaschaMann](https://discourse.julialang.org/u/SaschaMann)
#### Post date: [September 9, 2020, 3:43pm UTC](https://discourse.julialang.org/t/best-practices-for-testing-on-lts-and-latest-release-travis/46250/5 "2020-09-09T15:43:18Z")
Back then we decided against hardcoding it into the action, because one should not have to update the action to install a new Julia version. This matters when you vendor the action or pin it to a hash for security reasons. The versions are still hardcoded atm but hopefully at some point I’ll finally fix that. If the machine-readable julia version file that is/was in the works (would have to find the exact issue but it’s linked on the repo somewhere) would include it, or there was a separate file containing that info, we could include it easily.