# Is there a good reason to have an LTS version of Julia?

**URL:** https://discourse.julialang.org/t/is-there-a-good-reason-to-have-an-lts-version-of-julia/104179
**Category:** Internals & Design
**Created:** [September 23, 2023, 5:21pm UTC](https://discourse.julialang.org/t/is-there-a-good-reason-to-have-an-lts-version-of-julia/104179 "2023-09-23T17:21:19Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)
#### Post date: [September 26, 2023, 6:09pm UTC](https://discourse.julialang.org/t/is-there-a-good-reason-to-have-an-lts-version-of-julia/104179/18 "2023-09-26T18:09:22Z")

</div>

> [@lmiq](#):
>
> JuliaHub collects information about new installs of every package

Just to be abundantly clear here, it’s the community Julia Language Project package servers that collect and expose this anonymized information for anyone to use. JuliaHub is a consumer of this data:

> [@Announcing: package download stats!](https://discourse.julialang.org/t/announcing-package-download-stats/69073):
>
> After some years of getting the package server architecture in place and working (mostly) reliably, @staticfloat and I finally had some time to work on collecting logs into a data warehouse (we’re using [Snowflake](https://www.snowflake.com)) and designing a set of queries over the logs that we can run and publish regularly. The current public aggregated stats are available with the prefix https://julialang-logs.s3.amazonaws.com/public\_outputs/current/ followed by a rollup name and the suffix .csv.gz indicating that all t…

---

_[View the full topic](https://discourse.julialang.org/t/is-there-a-good-reason-to-have-an-lts-version-of-julia/104179)._