Hi The branches for camel-quarkus is not similar to the other Camel project / sub-projects
For example for camel-k, we have origin/release-1.0.x origin/release-1.1.x origin/release-1.2.x origin/release-1.3.x origin/release-1.4.x origin/release-1.5.x origin/release-1.6.x And for camel-karaf origin/camel-karaf-3.10.x origin/camel-karaf-3.11.x origin/camel-karaf-3.2.x origin/camel-karaf-3.3.x origin/camel-karaf-3.4.x origin/camel-karaf-3.5.x origin/camel-karaf-3.6.x origin/camel-karaf-3.7.x origin/camel-karaf-3.8.x origin/camel-karaf-3.9.x And so on In other words, we use a branch name with the major.minor.x as suffix. The camel-quarkus project does not, and we should get this aligned going forward origin/release-1.0.0-M6-attempt2 origin/release-1.0.0-M7 origin/release-1.0.0_M6-release4 origin/release/1.0.0 origin/release/1.0.0-CR2 origin/release/1.1.0 origin/release/1.2.0 origin/release/1.3.0 origin/release/1.4.0 origin/release/1.5.0 origin/release/1.6.0 origin/release/1.7.0 origin/release/1.8.0 origin/release/1.8.1 origin/release/2.0.0 origin/release/2.0.0-M1 origin/release/2.0.0-M2 origin/release/2.1.0 We should use .x so 2.1.0 is 2.1.x and so on. Also the last release is 2.2.0 and there is no branch for this. We need to get this aligned so we can ensure the website documentation is also maintainable. This file controls what gets published on the website https://github.com/apache/camel-website/blob/main/antora-playbook.yml -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
