-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mise à jour Erlang OTP (22->23) #1590
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thbar
added
the
dette technique
Entretien & maintenance générale, nécessaire pour que le code reste de bonne qualité
label
Apr 8, 2021
I have traced what OTP version could have been used by `elixir:1.11.3-alpine`. There is not a strict truth here yet, but: `erl -noshell -eval 'erlang:display(erlang:system_info(system_version))' -eval 'init:stop()'` provided a bit of partial information (e.g. Erlang/OTP 23 [erts-11.1.8] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1]), and then "erts-11.1.8" appears 5 times in https://github.com/erlang/otp/blob/master/otp_versions.table. I picked the most recent match.
thbar
changed the title
Mise à jour Erlang OTP de 22 à 23
Mise à jour Erlang OTP (22->23) et Elixir (1.10->1.11)
Apr 8, 2021
The previous one is not updated.
Extracted from #1515.
thbar
changed the title
Mise à jour Erlang OTP (22->23) et Elixir (1.10->1.11)
Mise à jour Erlang OTP (22->23)
Apr 8, 2021
This is required because I'm rebuilding the base image today, which installs at the moment the latest LTS.
Il reste un peu de test mais le gros est géré ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dette technique
Entretien & maintenance générale, nécessaire pour que le code reste de bonne qualité
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description finale de la PR
Cette PR:
Motivation à migrer Erlang OTP
Les problèmes rencontrés avec OTP 22 sont de deux ordres:
Je débute une mise à jour pour éviter de perdre davantage de temps plus tard, sachant qu'il faudra la faire de toute façon.
Je ne vais pour l'instant pas mettre à jour Elixir, car pour mettre à jour Elixir il faudra mettre à jour des librairies. Il existe un risque à ne pas mettre à jour tout en même temps, mais le travail est trop important par ailleurs.
Tâches restantes
Notes utiles
La page https://www.erlang.org/news/140 recense les incompatibilités, qui semblent limitées à SSL dans notre cas (et dont les changements nous arrangent, mais à vérifier).