[camel-k] branch main updated: Added some more post release steps

[ac...@apache.org]

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

acosentino 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 12137e2e1 Added some more post release steps
12137e2e1 is described below

commit 12137e2e1ad28f22cfdfa5153f7c5c7c9373e1e5
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Thu Oct 13 14:14:05 2022 +0200

    Added some more post release steps
---
 release.adoc | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/release.adoc b/release.adoc
index b96a995be..8ccba3299 100644
--- a/release.adoc
+++ b/release.adoc
@@ -52,16 +52,15 @@ Go to https://repository.apache.org/ and close the staging repository.
 
 A URL will be generated for the repository, like: https://repository.apache.org/content/repositories/orgapachecamel-xxxx. The URL needs to be communicated during the voting process.
 
+Now run:
 
-The apache-camel-k-runtime-<version>-source-release.zip file present in path `/org/apache/camel/k/apache-camel-k-runtime/<version>/` (and sha512 sum, if present) will need to be copied in the Apache dev SVN at https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/<version>.
-
-If the sha512 file is missing, one should be generated before committing to SVN.
-
-Commit all files to the SVN.
+```
+cd release-utils/scripts/
+./upload-sources.sh <released_version> <released_version>
+```
 
 Voting can start for camel-k-runtime, or a combined vote with camel-k can be started later.
 
-
 [[releasing-camel-k]]
 == Releasing Camel K
 
@@ -219,6 +218,13 @@ Apache dist repository on: https://dist.apache.org/repos/dist/release/camel.
 
 The same should be done for camel-kamelets and camel-k-runtime in case of combined vote.
 
+Both the camel-kamelets and camel-k-runtime contains a script to promote the release from dev to release
+
+```
+cd release-utils/scripts/
+./promote-release.sh <released_version>
+```
+
 Wait for maven mirrors to sync the new artifacts. This can take more than 1 hour sometimes.
 
 Binary files can be now released on Github, together with release notes generated in previous step.