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

commit ca780713cd66ba747ac6cc4d97901da84d345052
Author: Peter Palaga <[email protected]>
AuthorDate: Tue Apr 28 18:29:52 2020 +0200

    Update the release guide
---
 docs/modules/ROOT/pages/release-guide.adoc | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/pages/release-guide.adoc 
b/docs/modules/ROOT/pages/release-guide.adoc
index 0dfdb7c..8858377 100644
--- a/docs/modules/ROOT/pages/release-guide.adoc
+++ b/docs/modules/ROOT/pages/release-guide.adoc
@@ -2,7 +2,14 @@
 = Apache Camel Quarkus release process
 
 The process is _mutatis mutandis_ the same as for the main Apache Camel 
repository - see
-https://camel.apache.org/manual/latest/release-guide.html
+https://camel.apache.org/manual/latest/release-guide.html With Camel Quarkus, 
adding `-Prelease` to
+`release:prepare` and `release:perform` is not necessary. Given that you want 
to release version `0.1.0`,
+the release command would be the following:
+
+[source,shell]
+----
+$ mvn clean release:clean release:prepare -DreleaseVersion=0.1.0 
-DdevelopmentVersion=0.2.0-SNAPSHOT -B release:perform
+----
 
 In addition to the above, the following step is needed:
 

Reply via email to