This is an automated email from the ASF dual-hosted git repository.
nferraro 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 b2df77c chore(release): update release procedure
b2df77c is described below
commit b2df77c617be5e5067f2e11cc3a9b24bb115de9a
Author: nicolaferraro <[email protected]>
AuthorDate: Mon Jul 5 10:06:34 2021 +0200
chore(release): update release procedure
---
release.adoc | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/release.adoc b/release.adoc
index f902e6b..e2bb9d3 100644
--- a/release.adoc
+++ b/release.adoc
@@ -175,6 +175,9 @@ The release can be now announced to [email protected]
and [email protected].
A PMC member with access to the @ApacheCamel Twitter account should announce
the release on Twitter as well.
+Download section on the website needs to be put in sync to display the new
release.
+Checkout the website and put an entry under `content/releases/k` with the
version of the new release (copy the last release as template).
+The milestone field in the release doc is the Github id for the milestone
(e.g. for v1.4.1, the milestone is 22).
[[post-release]]
== Post Release
@@ -184,7 +187,7 @@ A PMC member with access to the @ApacheCamel Twitter
account should announce the
The https://github.com/operator-framework/community-operators[OperatorHub]
downstream channel should be synced to publish the latest version
of Camel K, so that it can be easily installed on platforms that support
Operator Hub.
-To do so, the content of `/deploy/olm-catalog/camel-k/<version>` (and package
manifest) should be uploaded to the "community-operators" repository (2 PRs,
one for OpenShift and one for all other platforms).
+You can create the bundle using the `make bundle` command, then upload the CRD
and CSV to the "community-operators" repository (2 PRs, one for OpenShift and
one for all other platforms).
=== Helm