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

[camel-k] branch release-1.11.x updated: Upgrade release.adoc with instruction about upload/promote sources

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

acosentino pushed a commit to branch release-1.11.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git


The following commit(s) were added to refs/heads/release-1.11.x by this push:
     new ccb541692 Upgrade release.adoc with instruction about upload/promote sources
ccb541692 is described below

commit ccb54169224ddead7e4da15888f0a798e327a624
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Dec 12 13:54:32 2022 +0100

    Upgrade release.adoc with instruction about upload/promote sources
    
    Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
 release.adoc | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/release.adoc b/release.adoc
index b3e926664..8304fa06a 100644
--- a/release.adoc
+++ b/release.adoc
@@ -127,18 +127,15 @@ make release-staging
 ```
 
 Binary files will be generated and put in the project root directory, including examples.
-All those files should be put in the corresponding directory of the camel-k dev SVN at https://dist.apache.org/repos/dist/dev/camel/camel-k/<version>.
 
-Sources are not produced directly by the scripts, but since the procedure is creating a tag, the source code in tar.gz format can be downloaded from Github
-at: https://github.com/apache/camel-k/releases
-
-After copying all the files to the dev SVN, a `sign.sh` script in the parent directory can be used to sign all the uploaded artifacts:
+Now run:
 
 ```
-./sign.sh <version> <gpg_pass>
+cd release-utils/scripts/
+./upload-sources.sh <released_version> <released_version>
 ```
 
-Commit all files to the SVN.
+This will upload the sources, client and examples to the dist/dev repository in ASF.
 
 A docker image `camelk/camel-k:<version>` will be pushed to the staging organization (`camelk`, not `apache`).
 
@@ -229,7 +226,7 @@ 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
+Camel-kamelets, camel-k-runtime and camel-k contains a script to promote the release from dev to release
 
 ```
 cd release-utils/scripts/