Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Raising the minimum tested version of OCaml to 4.05 or 4.08 #259

Open
tmcgilchrist opened this issue Jan 16, 2024 · 5 comments
Open

Raising the minimum tested version of OCaml to 4.05 or 4.08 #259

tmcgilchrist opened this issue Jan 16, 2024 · 5 comments
Assignees
@shonfeder
Labels
capacity+ Work that will increase our capacity (by reducing workload or increasing our efficacy)

Comments

@tmcgilchrist
Copy link
Member

Based on this old thread https://discuss.ocaml.org/t/raising-the-minimum-tested-version-of-ocaml-to-4-05-or-4-08-from-4-02/12464 from @avsm opam-repo-ci should consider upgrading the lower bound of supported OCaml versions to save some wasted compute time.
@benmandrew benmandrew mentioned this issue Jan 24, 2024
Open
@shonfeder shonfeder self-assigned this May 27, 2024
@shonfeder
Copy link
Contributor

I will mention this at the opam repo maintenance meeting.

@shonfeder
Copy link
Contributor

Opam repo maintainers said that this was part of ocaml/opam-repository#23789

@mseri
Copy link
Contributor

mseri commented Jul 10, 2024

I am in favour of already raising this to 4.08

@shonfeder shonfeder added the capacity+ Work that will increase our capacity (by reducing workload or increasing our efficacy) label Jul 10, 2024
@punchagan
Copy link
Contributor

We're starting to see base image build failures with newer OS's (using GCC 14) with OCaml < 4.08. See ocurrent/docker-base-images#279

opam-repo-ci runs the tests on Debian 12 with GCC 12, so this isn't a problem. But, it just adds another datapoint about support OCaml versions < 4.08.

@punchagan
Copy link
Contributor

I am in favour of already raising this to 4.08

The plan for deprecation is here and a draft policy for similar updates in future is here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shonfeder shonfeder

Labels
capacity+ Work that will increase our capacity (by reducing workload or increasing our efficacy)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tmcgilchrist @punchagan @mseri @shonfeder