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.

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

Create CI builds against GDAL 3.6 & 3.7 #403

Closed
metasim opened this issue May 19, 2023 · 5 comments · Fixed by #412
Closed

Create CI builds against GDAL 3.6 & 3.7 #403

metasim opened this issue May 19, 2023 · 5 comments · Fixed by #412
Milestone

Comments

@metasim
Copy link
Contributor

metasim commented May 19, 2023

Should we consider dropping 3.2 and/or 3.3? Under what principles should we make that evaluation?

@metasim metasim added this to the 0.15 milestone May 22, 2023
@jdroenner
Copy link
Member

This is a really good question. My idea was to have a test for the GDAL included in the current Ubuntu LTS. (and all GDAL versions released after that).

@lnicola
Copy link
Member

lnicola commented May 31, 2023

Nominating this for the new release, since the 3.7 bindings are broken.

bors bot added a commit that referenced this issue Jun 1, 2023
412: Add `GDT_Int8`, test GDAL 3.7 on CI and refactor workflow r=metasim a=lnicola

- [x] I agree to follow the project's [code of conduct](https://github.com/georust/gdal/blob/master/CODE_OF_CONDUCT.md).
- [x] I added an entry to `CHANGES.md` if knowledge of this change could be valuable to users.
---

Closes #403


Co-authored-by: Laurențiu Nicola <[email protected]>
@metasim
Copy link
Contributor Author

metasim commented Jun 1, 2023

Fixed in #412

@metasim metasim closed this as completed Jun 1, 2023
@lnicola
Copy link
Member

lnicola commented Jun 1, 2023

The current Ubuntu LTS would be 22.04, right?

@jdroenner
Copy link
Member

yes 22.04 is the latest LTS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants