You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pc...@apache.org on 2022/12/21 15:52:48 UTC

[camel-k] 02/02: chore(doc): automatic updates

This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git

commit 7fb4d1298db06d4c30f440027bdc08b66d4526df
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Wed Dec 21 14:27:45 2022 +0100

    chore(doc): automatic updates
---
 release.adoc | 31 ++++---------------------------
 1 file changed, 4 insertions(+), 27 deletions(-)

diff --git a/release.adoc b/release.adoc
index b5c36c8c3..3639da76c 100644
--- a/release.adoc
+++ b/release.adoc
@@ -72,7 +72,7 @@ Next, the version of the runtime libraries to use need to be aligned in the Make
 
 The following tasks need to be done:
 
-- Align `KAMELET_CATALOG_REPO_BRANCH` in Makefile to latest released tag of the camel-kamelets repository
+- Align `KAMELET_CATALOG_REPO_TAG` in Makefile to latest released tag of the camel-kamelets repository
 - Align `RUNTIME_VERSION` in Makefile to latest runtime release
 - Set `STAGING_RUNTIME_REPO` to the URL of the staging repo (if using a staged camel-k-runtime version)
 - Ensure `LAST_RELEASED_VERSION` points to latest released version of Camel K
@@ -173,32 +173,9 @@ A `release-notes.md` file is generated and can be attached to the release github
 [[documentation]]
 == Documentation updates
 
-In order that the newly released versions of camel-k and camel-k-runtime appear in the Camel website, follow these steps:
-
-. In camel-k `docs/antora.yml`:
-.. Set the `version` appropriately, e.g. `1.7.x`
-.. Remove the `prerelease` and `display_version`.
-.. Set the `asciidoc.attributes.camel-version` to the appropriate released camel docs version, e.g. `3.12.x`.
-. In the camel-k-runtime corresponding to the camel-k release `docs/antora.yml` set the `version` to the same value as in step 1.a.
-. After the vote has passed, update the camel-website `antora-playbook.yml`
-`content.sources` section for camel-k and camel-k-runtime to use the newly released versions, replacing the previous released version.
-
-NOTE: this needs work, 1.6.x doesn't appear to have a corresponding camel-k-runtime
-[source,yaml]
-----
-    - url: https://github.com/apache/camel-k.git
-      branches:
-        - main
-#        Release-1.6.x does not work because there is no corresponding camel-k-runtime version for languages.
-#        - release-1.6.x
-        - release-1.4.x
-      start_path: docs
-
-    - url: https://github.com/apache/camel-k-runtime.git
-      branches:
-        - main
-      start_path: docs
-----
+The version of Camel K and the main related dependencies are scraped automatically in a Github Action. You only need to provide the LTS parameter in the related `release` branch, when the release is marked as LTS (such as in https://github.com/apache/camel-k/blob/f15124949e43bb859d07f555b9e510956d6ed823/docs/antora.yml#L30)
+
+After the vote has passed, update the camel-website `antora-playbook.yml` `content.sources` section for camel-k and camel-k-runtime to use the newly released versions, replacing the previous released version.
 
 [[voting]]
 == Voting