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 078a668 Improve the Release guide
078a668 is described below
commit 078a66831a4ce149f336392f8d7fdf7ab766abbf
Author: Peter Palaga <[email protected]>
AuthorDate: Mon Aug 10 11:53:31 2020 +0200
Improve the Release guide
---
.../pages/contributor-guide/release-guide.adoc | 39 +++++++++++++++++-----
1 file changed, 31 insertions(+), 8 deletions(-)
diff --git a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
index c7d9a7e..21f2acb 100644
--- a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
@@ -2,17 +2,40 @@
= Apache Camel Quarkus release process
:page-aliases: release-guide.adoc
-The process is _mutatis mutandis_ the same as for the main Apache Camel
repository - see
-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:
+The process is _mutatis mutandis_ the same as for the main Apache Camel
repository - see the
+https://camel.apache.org/manual/latest/release-guide.html[Release guide] page
of the Camel documentation.
+
+Here, just a sketch of the repeating part, after you have performed the
initial setup following the
+https://camel.apache.org/manual/latest/release-guide.html[Camel Release guide].
+
+== Create a release branch
+
+[source,shell]
+----
+$ export VERSION=... # the version you are releasing, e.g. 0.1.0
+$ export NEXT_VERSION=... # the next development iteration, e.g. 0.1.1-SNAPSHOT
+$ git fetch upstream # upstream is [email protected]:apache/camel-quarkus.git
+$ git checkout master # master is the branch from which you want to release
+$ git reset --hard upstream/master # make sure you are in sync with upstream
+$ git checkout -b release/$VERSION
+----
+
+== `release:prepare` and `release:perform`
+
+With Camel Quarkus, adding `-Prelease` to `release:prepare` and
`release:perform` is not necessary,
+because all necessary profiles are set in the configuration of the
`maven-release-plugin`.
+
+The Maven command to release is as follows:
[source,shell]
----
-$ mvn clean release:clean release:prepare -DreleaseVersion=0.1.0
-DdevelopmentVersion=0.2.0-SNAPSHOT -B release:perform
+$ mvn clean release:clean release:prepare -DreleaseVersion=$VERSION
-DdevelopmentVersion=$NEXT_VERSION -B release:perform
----
-In addition to the above, the following step is needed:
+== Further steps
+
+In addition to the above, the following is needed:
-* After releasing the staging repository on https://oss.sonatype.org, update
the value of `camel-quarkus-last-release`
-attribute in the camel-quarkus
https://github.com/apache/camel-quarkus/blob/master/docs/antora.yml#L25[antora.yml
component descriptor].
+* After releasing the staging repository on
https://repository.apache.org[https://repository.apache.org], update the
+value of `camel-quarkus-last-release` attribute in the camel-quarkus
+https://github.com/apache/camel-quarkus/blob/master/docs/antora.yml#L25[antora.yml
component descriptor].
