Either way seems like a good progress to me. Thank you! Il giorno mar 27 ott 2026 alle ore 01:50 Maxim Solodovnik < [email protected]> ha scritto:
> IMO having old version in test stack is good for compatibility > > So I would vote for #2 :) > > from mobile (sorry for typos ;) > > > On Tue, Oct 27, 2026, 01:32 Richard Zowalla <[email protected]> wrote: > > > Hi all, > > > > the scheduled Databases workflow (OPENJPA-3011) and the test-*-docker > > profiles in pom.xml test against: > > > > - PostgreSQL 11 (end of life since November 2023) > > - MySQL 8.0 (end of life since April 2026) > > - MariaDB 11.8 (LTS, supported) > > > > The PostgreSQL version goes back to the 2018 profile (OPENJPA-2753), and > > the workflow took it over from there. Results on an unsupported server > are > > not very useful: a failure there may already be fixed in the database, > and > > nobody should run production on it. > > > > I'd like to move to supported versions. Two options: > > > > 1. Latest only: PostgreSQL 18, MySQL 8.4 LTS, MariaDB 11.8. One job per > > database, as today. > > 2. Oldest supported + latest: for example PostgreSQL 15 and 18, MySQL 8.4 > > and 9.x, MariaDB 10.11 and 11.8. This catches both dialect regressions on > > older servers and changes in new releases, but doubles the jobs (it runs > > once a week, so the cost is limited). > > > > I'd prefer option 2. Option 1 would be the minimum. > > > > The PostgreSQL job currently fails. I'm looking into it against 11 first, > > so we know whether the failures come from OpenJPA or from the old server, > > and will report back. > > > > Opinions? > > > > Gruß > > Richard > -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA https://about.me/ilgrosso <http://home.apache.org/~ilgrosso/>
