Quarkus 3.8 LTS release

[turing85]

When the next LTS (3.8.0) lands, we need to:

• [x] branch a 3.1.x-branch before merging the PRs for quarkus-bom and quarkus-camel-bom,
• [x] merge the aforementioned PRs into main,
• [x] Update docs/modules/ROOT/pages/quarkus-artemis-jms.adoc with the new information wrt. version support and LTS support,
• [x] Update .github/dependabot.yml on main to fixate the quarkus-version for 3.1.x to be < 3.8,
• [x] downstream the last two points to all branches,
• [x] Update docs/antora.yml on the new 3.1.x branch and set its version to 3.1.x,
• [x] Update the antora-playbook.yml (github.com) to include the new 3.1.x branch, and
• [x] Produce a new minor release 3.2.0,

When the next non-LTS release (probably 3.9.0) lands, we need to:

• [x] branch a 3.2.x-branch before merging the PRs for quarkus-bom and quarkus-camel-bom,
• [x] set the version in antora.yml on the new branch 3.2.x from main to 3.2.x,
• [x] merge the aforementioned PRs into main,
• [x] Update docs/modules/ROOT/pages/quarkus-artemis-jms.adoc with the new information wrt. version support,
• [x] Update .github/dependabot.yml on main to fixate the quarkus-version for 3.2.x to be < 3.9,
• [x] downstream the last two points to all branches,
• [x] Update docs/antora.yml on the new 3.2.x branch and set its version to 3.2.x,
• [x] Update the antora-playbook.yml (github.com) to include the new 3.2.x branch. and
• [x] Produce a new minor release 3.3.0,
• [ ] With the next 3.2.x-release set the next-version in project.yml on branch 3.2.x from 999-SNAPSHOT to 3.2.x-999-SNAPSHOT

@middagj, @zhfeng, @louisa-fr Please feel free to add you opinions and other discussion points.

[turing85]

For quarkus 2.13, the maintenance supports end 2024-04-30. I propose we stop supporting branch 2.x at the same date. This would mean that we:

• remove the branch from .github/dependabot.yml in branch main
• update docs/modules/ROOT/pages/quarkus-artemis-jms.adoc to mark 2.x as EOL,
• downstream the changes to all branches, and
• produce a final release of branch 2.x, with all updates.

WDYT?

[turing85]

3.8.0.CR1 just landed. I branched 3.1.x, updated the dependabot.yml on main, updated the docs on main, updated quarkus and camel-quarkus to 3.8.0.CR1 on main. The build for our release 3.2.0.CR is underway. The relevant changes are downstreamed to branches 2.x, 3.0.x and 3.1.x. In short: we are all set :slightly_smiling_face: