[camel-k] branch release-up-1.10.x created (now 8a4416e5b)

[ac...@apache.org]

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

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


      at 8a4416e5b Upgrade release.adoc with instruction about upload/promote sources

This branch includes the following new commits:

     new 8a4416e5b Upgrade release.adoc with instruction about upload/promote sources

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[camel-k] 01/01: Upgrade release.adoc with instruction about upload/promote sources

[ac...@apache.org]

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

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

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

    Upgrade release.adoc with instruction about upload/promote sources
---
 release.adoc | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/release.adoc b/release.adoc
index 93389135c..9ae35f423 100644
--- a/release.adoc
+++ b/release.adoc
@@ -128,18 +128,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`).
 
@@ -228,7 +225,12 @@ docker push apache/camel-k:$VERSION
 Artifacts committed on https://dist.apache.org/repos/dist/dev/ before the voting process need to be copied to the
 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.
+Camel-kamelets, camel-k-runtime and camel-k 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.