search

JuliaLang / Downloads.jl

MIT License
89 stars 34 forks source link

current version does not match available version or Julia version #238

Closed lmiq closed 3 months ago

lmiq commented 3 months ago

Since this package is one shipped in the Julia image, shouldn't it provide versions with the same number as the Julia versions, as other packages?

In parallel, here current stable version is 1.5.3, but in Julia 1.10 it seems that 1.6.0 is shipped. I'm confused about that, while trying to test some package with downgraded versions.

giordano commented 3 months ago

This is the case for many stdlibs.

lmiq commented 3 months ago

That the version necessary in the [compat] entry does not match any version available in the site? How can one know than what to add to the compat entry?

lmiq commented 3 months ago

Well, just leave it, I'm confused about some stdlibs having true versions, others not, and now a little bit more by those that do have true versions may not match the actual package versions.

giordano commented 3 months ago

To be clear, I think it'd be better to have proper version numbering for this package (last change was three years ago), but it doesn't necessarily have to follow julia's version number.

StefanKarpinski commented 3 months ago

Yeah, I got a bit lazy about making releases; it's annoying to keep up, especially with backports to LTS, which makes the release sequence non-linear.

DilumAluthge commented 3 months ago

Yeah, I got a bit lazy about making releases; it's annoying to keep up, especially with backports to LTS, which makes the release sequence non-linear.

Ideally we would have tooling to automate most of the release process for external stdlibs. Especially as we start moving more and more stdlibs out to their own repos.