anchor.diff:  Branches should be listed in reverse release order, newest first, preceded by the `main` prerelease branch.
   
   First release after an LTS release::
  -* Add a new branch in the sources sections for camel, camel-karaf, and camel-spring-boot between `main` and the last LTS release branch.+* Add a new branch in the sources sections for camel, camel-karaf, and camel-spring-boot between `main` and the last LTS release branch.
  +
  +=== Test your work!
  +
  +Create branches for each changed branch, push them, use those branches in your playbook, commit the playbook in a branch and push it, and open a PR for the playbook to find out if you missed anything.
  +Wait for the PR build and netlify preview and check that the build succeeded and the preview looks good.
  
positive.code: Changes to both `main` and the new branch, say `camel-3.12.x`, will be needed.
  The changes are almost the same whether the new branch is LTS or not.
  
  === Changes to `main` branch
  
  In `camel:docs/components/antora.yml`::
  In `camel-karaf:docs/antora.yml`::
  In `camel-spring-boot:docs/antora.yml`::
  Increment the display-version, e.g. `3.12.x (Prerelease)`  to `3.13.x (Prerelease)`
  
  === Changes to the new branch (`3.12.x`)
  
  In `camel:docs/components/antora.yml`::
  In `camel-karaf:docs/antora.yml`::
  In `camel-spring-boot:docs/antora.yml`::
  * Change `version` to the branch name e.g. `3.12.x`
  * Remove the `prerelease` flag line
  * If the new branch is LTS, set the display-version to e.g. `3.12.x (LTS)`.
  * If the new branch is not LTS, remove the `display-version` line.
  
  In `camel-karaf:tooling/camel-karaf-docs-maven-plugin/src/main/java/org/apache/camel/karaf/maven/ExtMvelHelper.java`::
  In `camel-spring-boot:tooling/camel-spring-boot-docs-maven-plugin/src/main/java/org/apache/camel/springboot/maven/ExtMvelHelper.java`::
  
  change
  +
  [source,java]
  private final static String CAMEL_VERSION = "latest";`
  +
  to e.g.
  +
  
negative.code: == Notes on versions
  
  Within an Antora component, xrefs to content in the same component, whether or not they are in the same source tree or repository, should never include the `version` or `component` segment of the page id.
  Including the version will make the page non-relocatable to another version: for instance specifying `next` in the main branch will break the link when main is branched for a release.
  Including the `component` segment will redirect to the (Antora) latest version, which will typically be the last released version.
  
  Antora calculates the latest version as the last non-prerelease version.
  Since we are marking the main branch as prerelease, this will never be the main branch.
  
  == After a new release branch is created
  
  