Julia 1.6 was released on 24 March 2021, but wasn’t declared LTS until Dec 2021 (previous LTS, 1.0, was LTS for just over 3 years). Should we go for 18 month LTS support as node.js? There has never been a promise for how long long-term support means for Julia (and I’m not even sure how desirable an…

Barring bad (thus far unseen) problems with the release, Julia 1.10 is very likely to become the new LTS once we’ve gotten a couple of point releases out for it. So far there’s a bit of a kerfuffle about artifact hash mismatches making 1.10.0 unusable for Windows users not using Developer Mode, but …

[image] mbauman: it means that there’s a branch onto which backports can land and from which a new patch release might be cut. That’s also exactly the support that the most recent release gets. Sure, but it also means: If a bad bug is discovered, then there will be another release. If people …

Are there statistics out there to try to tease out how often used LTS is versus other releases? Like do the package download stats provide the Julia version which is used to install the package?

Yes, it does. Here’s the super-naive thing of just the total number of requests over the past 365 days and since Jan 1 ▶ code [image] [image]

[image] foobar_lv2: Being on an LTS inside the support window guaranteed that such a patch would be forthcoming (in reality the patch came before LTS became relevant, so I’d classify that as a near-miss). AFAIK there are no such explicit guarantees for Julia. What you get with Julia LTS is th…

I no longer use 1.6, I always use latest stable, and/or master. My point is that package developers should disregard 1.6, but also make packages for 1.11 which means disregarding 1.11 1.10. 1.10 without “public” shouldn’t hold back good software development, or make it any more difficult to support…

[image] Palli: also make packages for 1.11 which means disregarding 1.11 Sorry, my mastery of Zen Buddhism is not sufficient to understand this koan. [image] Palli: What’s the point of LTS? Julia’s Release Process Julia’s Release Process | People involved in the day-to-da…

I had a typo (now fixed), I meant “make packages for 1.11 which means disregarding 1.10”, meaning good packages for 1.11 use public (where applying) and by doing such disregard 1.10 users by default, or make work for themselves to support older releases too, that would be avoided if LTS has support …

There are always new goodies that folks will want from newer releases (see, e.g., v1.7 ). That’s a good thing. That’s something you explicitly sacrifice in choosing to use any LTS of any software. Yes, many packages choose to use Julia’s LTS marker to drive their own development practices. But th…

[image] Palli: good packages for 1.11 use public (where applying) and by doing such disregard 1.10 users by default Generally if you need a feature present from Julia 1.11, you will need to either lower bound the Julia version in compat or use Compat.jl if possible. This does not “disregard”…

New Julia LTS? Are many using the current (Julia 1.6) LTS?

General Usage

goerz January 18, 2024, 12:11pm 52

Someone could probably implement a macro @public that does the same as @compat public but is slightly prettier, no?

Topic		Replies	Views
Next Julia LTS; when? General Usage	16	2086	October 19, 2021
Is there a good reason to have an LTS version of Julia? Internals & Design	22	2642	September 29, 2023
What are the current plans regarding a new LTS Julia version? Internals & Design	33	3777	June 26, 2021
Is 1.10 going to be the next LTS? Community	7	681	August 26, 2024
Proposed release process and schedule Internals & Design proposal , releases	39	9360	January 25, 2019

New Julia LTS? Are many using the current (Julia 1.6) LTS?

Related topics