axelson
I’m curious how many minor Elixir versions library authors generally try to support. I’m thinking that a good default is 3 minor versions which will equate to roughly 1.5 years (and is the approach mentioned in Library builders: What versions of Elixir to support? When to stop supporting older Elixir versions? - #3 by Qqwy). And of course the previous versions of a library are still available for users that are unable to upgrade elixir for some reason.
Where Next?
Trending in Discussions
Other Trending Topics
Chat & Discussions>Discussions
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
benwilson512
@axelson I’m also a fan of supporting basically 2 major versions of a lib that have different Elixir version reqs. Eg: some library named Foo that has:
It depends a bit on how important new Elixir features are to your app.
dimitarvp
I’d support anything I could but it depends how easy it would be to just copy-paste the functions from newer Elixir releases to a dedicated
Compatmodule namespace. I am entertaining the idea for a long time and I think it can work out fine.Having said that, I’d aim for current version plus 2 versions behind, e.g. 1.12, 1.11 and 1.10.
stratacast
Mind if I hijack the thread to get some clarity? Say 1.9-1.11 your library works, but 1.12 breaks it. In your example, I could create a 1.6.x branch and specify it as tested for 1.12, but how would that work for something like hex.pm? It would only display the latest version of my lib, wouldn’t it? And would that be left up to the developer to see that they’d have to downgrade their version?