anchor.diff:  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
  +=== Changes to the new branch (`3.12.x`)
  +
  +For each of the projects, `camel`, `camel-karaf`, `camel-spring-boot`, locate the section for the project in the `camel-website` `antora-playbook.yml` and adjust the version in the component descriptor for each start path.
  +As of writing this consists of:
   
   In `camel:docs/components/antora.yml`::
  +In `camel:core/camel-core-engine/src/main/docs/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)`
  +In `camel-spring-boot/components-starter/antora.yml`::
  +In `camel-spring-boot/core/antora.yml`::
  +In `camel-spring-boot/docs/components/antora.yml`::
  +In `camel-spring-boot/docs/spring-boot/antora.yml`::
   
  -=== 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";`
  +private final static String CAMEL_VERSION = "next";`
   +
   to e.g.
   +
  
positive.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 `latest` 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, although the version is currently 'latest'.
  
  == After a new release branch is created
  
  
negative.code: 
  NOTE: TODO: Is there a step of setting up CI or the regen bot?
  Should maven snapshots be deployed?
  
  In the `camel-quarkus` project examine the root `pom.xml` of every version used in the website.
  There will be a property entry like:
  
  [source,xml]
          <!-- Primary dependencies - maintained manually -->
          <camel.major.minor>3.13</camel.major.minor> <!-- run after each change: cd docs && mvnd validate -->
  
  If the camel version is removed from documentation by this release, update it to the new version.
  If the camel version is LTS consider whether it is appropriate to update it to the new version.
  If changed, follow the instructions and run mvn validate in the docs directory.
  
  === Changes to the Antora playbook
  
  