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
The following commit(s) were added to refs/heads/main by this push:
new 57896be72 chore(doc): release documentation process
57896be72 is described below
commit 57896be728b541660ee0d72a2689d58e716745f4
Author: Pasquale Congiusti <pasquale.congiu...@gmail.com>
AuthorDate: Tue Oct 24 09:19:05 2023 +0200
chore(doc): release documentation process
---
release.adoc | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/release.adoc b/release.adoc
index 8b17f9d35..adb72b80e 100644
--- a/release.adoc
+++ b/release.adoc
@@ -199,9 +199,11 @@ The release can be now announced to d...@camel.apache.org
and users@camel.apache.
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.
+After the vote has passed you should update camel-website project:
-You also need to create an entry in the release section of Camel website
project: https://github.com/apache/camel-website/tree/main/content/releases/k -
you can use any previous document as a reference.
+1. update the
https://github.com/apache/camel-website/blob/main/antora-playbook-snippets/antora-playbook.yml[camel-website
`antora-playbook.yml` `content.sources` section] for camel-k to use the newly
released versions, replacing the previous released version or any unsupported
version.
+1. create an entry in the release section of Camel website project:
https://github.com/apache/camel-website/tree/main/content/releases/k - you can
use any previous document as a reference.
+1. provide a blog post announcing the release
NOTE: the milestone is the github project milestone ID used to track the
release.
