[camel-quarkus] branch master updated: Improve the release guide

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[camel-quarkus] branch master updated: Improve the release guide

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

ppalaga pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git


The following commit(s) were added to refs/heads/master by this push:
     new 6966fb6  Improve the release guide
6966fb6 is described below

commit 6966fb61e38fbc5c3e61a1c85f4655f6f7a8acdd
Author: Peter Palaga <[hidden email]>
AuthorDate: Tue Feb 23 10:46:59 2021 +0100

    Improve the release guide
---
 .../ROOT/pages/contributor-guide/release-guide.adoc    | 18 +++++++++++++-----
 1 file changed, 13 insertions(+), 5 deletions(-)

diff --git a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
index f850cb1..87e35be 100644
--- a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
@@ -86,10 +86,18 @@ In case you have performed the above step during some release in the past, you n
 
 [source,shell]
 ----
-$ svn update 'https://dist.apache.org/repos/dist/release/camel' camel-releases-dist
+$ cd camel-releases-dist
+$ svn update .
 ----
 
-Make sure your public key is present in the `KEYS` file. Add it, if it is not there yet.
+Make sure your public key is present in the `KEYS` file. Add it, if it is not there yet using `gpg` command:
+
+[source,shell]
+----
+$ export EMAIL= # the e-mail address in your key
+$ gpg -k $EMAIL >> KEYS
+$ gpg --armor --export $EMAIL >> KEYS
+----
 
 Assemble the Apache Camel Quarkus distribution:
 [source,shell]
@@ -126,9 +134,9 @@ $ svn commit -m "Apache Camel Quarkus $VERSION released artifacts"
 
 In addition to the above, the following is needed:
 
-* When writing the release announcement blog post, do not forget to add the release note section in https://github.com/apache/camel-website/tree/master/content/releases/q
-* https://github.com/apache/camel-quarkus/issues/new[Create a ticket] asking a https://projects.apache.org/committee.html?camel[PMC member] to update the https://reporter.apache.org/addrelease.html?camel[Apache Committee Report Helper]. The ticket title could be as follow.
-  Release: The Apache Committee Report Helper should be updated by a PMC member as camel-quarkus-X.Y.Z has been released on YYYY-MM-DD.
 * Check the state of `camel-quarkus-master` branch in the
   https://github.com/apache/camel-quarkus-examples[Examples repository]. If the version properties are in sync with
   new Camel Quarkus release and if the tests are passing, merge `camel-quarkus-master` to `master`.
+* https://github.com/apache/camel-quarkus/issues/new[Create a ticket] asking a https://projects.apache.org/committee.html?camel[PMC member] to update the https://reporter.apache.org/addrelease.html?camel[Apache Committee Report Helper]. The ticket title could be as follow.
+  Release: The Apache Committee Report Helper should be updated by a PMC member as camel-quarkus-X.Y.Z has been released on YYYY-MM-DD.
+* When writing the release announcement blog post, do not forget to add the release note section in https://github.com/apache/camel-website/tree/master/content/releases/q