You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We faced some issues when using postgis 3.2 and 3.3 images for CI purposes to have a look at our users that have maybe not upgraded to the latest postgis versions :
We financed a bug fix identified in 3.2, 3.3, 3.4 latest versions and it was backported to these versions.
As I understand, only 3.4 images are now updated on docker. Since docker images are a powerful tool for CI, it means to me that the only supported version is 3.4 since we can't test on older versions.
Is it a wish or a constraint?
The result for us is :
3.2 image is too old and has not the bug yet
3.3 image is exactly on the bug ("broken")
3.4 is up to date and is fixed
What should I assume as current and available versions to use with postgis dockerised in 2024 - 2025 - ... ?
Hi,
We faced some issues when using postgis 3.2 and 3.3 images for CI purposes to have a look at our users that have maybe not upgraded to the latest postgis versions :
teksi/wastewater#20
We financed a bug fix identified in 3.2, 3.3, 3.4 latest versions and it was backported to these versions.
As I understand, only 3.4 images are now updated on docker. Since docker images are a powerful tool for CI, it means to me that the only supported version is 3.4 since we can't test on older versions.
The result for us is :
3.2 image is too old and has not the bug yet
3.3 image is exactly on the bug ("broken")
3.4 is up to date and is fixed
What should I assume as current and available versions to use with postgis dockerised in 2024 - 2025 - ... ?