Quarkus 2.0 and Java 11 considerations

[lwitkowski]

Quarkus 2.0 is in Release Candidate state as of today, and it's a matter of days until it becomes Final. It supports (and requires) Java 11, and if we still want to support Quarkus 1.X (java 1.8) we will have to maintain 2 versions (sources and artifacts in maven central).

One possible approach is to branch version for quarkus 1.X from master today (let's call this branch quarkus_1.X), optionally bump it to v1.0.0, then - once Quarkus 2.0 is out - merge #126 to master, and release as v2.0.0. All bugfixes and possibly feature will have to be backported to quarkus_1.X, then released as 1.X.Y to maven central.

Good news is #126 uses Quarkus 2.0 and all tests are green now :)

Need your feedback here @pazkooda @Wertros

[lwitkowski]

v1.0.0 has just been released, and this tag can be a base for a branch in the future once we merge quarkus 2.0 compatibility to master.

[lwitkowski]

v1.X has just been branched. master branch is switched to Quarkus 2.0 / Java 11. I've also pre-released v2.0.0.CR3 for testing purpose and pushed it to Maven Central.

All bugfixes and features can/should be backported to v1.X branch and released to Maven Central as v1.X.Y

[lwitkowski]

v2.0.0 released, discussion closed.