Discontinue quarkus-artemis 2.x

turing85 commented 4 months ago

Quarkus 2.13 reaches its EOL on 2024-04-30 (see here (access.redhat.com)).

On this day, we should:

[x] produce one final release of quarkus-artemis 2.x (probably version 2.1.4)
[x] add an additional tag (2.x-discontinued) over on the same commit of the final relese
[x] remove the branch 2.x from quarkivese-doc's antora-playbook.ym, add the last release tag
[x] remove the backport/2.x label
[x] remove the 2.x-branch
[ ] (a day or so later) Verify that the branch 2.x has been replaced by the tag on https://docs.quarkiverse.io/quarkus-artemis/dev/index.html

Questions:

Should we also delete the branch? We would still have the tags, so the code should still be present. It is possible to point the antora-playbook.yml (github.com) against a tag (see here (docs.antora.org)). In this case, we would need to open a PR against https://github.com/quarkiverse/quarkiverse-docs. @gastaldi do you know whether referencing tags may cause issue with the current setup? It seems that nobody uses tags as of now. -> Yes, we want to delete the branch

@middagj, @zhfeng what do you think about deleting the branch?

gastaldi commented 4 months ago

@turing85 I don't think referencing tags is a problem if Antora supports it

middagj commented 4 months ago

If we are not going to continue I would delete the branch. We have tags so we don't lose the commits on cleaning.

quarkiverse / quarkus-artemis