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'll want to wait for RHBQ 3.7/3.8 to be out, because migrating now would mean downgrading from Quarkus 3.6 to 3.2, and that would mean some annoying changes in tests.
The text was updated successfully, but these errors were encountered:
Now we'd have to wait for a 3.10+ as we are using the standalone mapper.
And thinking more about this particular one, do we really want to stay on a RHBQ version or stay on the latest available and be able to test any new features we add to Search on a real application?
do we really want to stay on a RHBQ version or stay on the latest available and be able to test any new features we add to Search on a real application?
Depends who "we" is. Personally, I'd vote for always using the latest. But I understand the core Quarkus team may want to focus testing on LTS.
I think we'll probably end up doing this only if some compelling arguments show up, or if someone else who thinks it's a good idea actually puts in the work to maintain this project.
See https://access.redhat.com/documentation/en-us/red_hat_build_of_quarkus/quarkus-3.2/guide/8c2d0754-31e2-4d6d-9d5f-9ade55c3b30d for instructions for 3.2; it'll probably be similar for later versions.
We'll want to wait for RHBQ 3.7/3.8 to be out, because migrating now would mean downgrading from Quarkus 3.6 to 3.2, and that would mean some annoying changes in tests.
The text was updated successfully, but these errors were encountered: