This is an automated email from the ASF dual-hosted git repository.
aldettinger 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 2b72581 Updated the release guide in order to publish sources
2b72581 is described below
commit 2b72581fe6ffec2dc8dce49ed2daf0002db53d16
Author: aldettinger <aldettin...@gmail.com>
AuthorDate: Wed Dec 2 18:30:27 2020 +0100
Updated the release guide in order to publish sources
---
.../pages/contributor-guide/release-guide.adoc | 41 +++++++++++++++++++++-
1 file changed, 40 insertions(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
index bcae842..21cc7c1 100644
--- a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
@@ -41,12 +41,51 @@ $ mvn clean release:clean release:prepare
-DreleaseVersion=$VERSION -Ddevelopmen
In case `release:prepare` is successful but an issue occurs during
`release:perform`, it could be worth trying to resume from the failing artifact.
For instance, would an issue occurs while performing the release of
`camel-quarkus-openapi-java`, a resume attempt could be triggered as below:
-
[source,shell]
----
$ mvn -DskipTests -Denforcer.skip -Dquarkus.build.skip -Dformatter.skip
-Dimpsort.skip deploy -Papache-release -rf :camel-quarkus-openapi-java
----
+== Update the Apache Camel Quarkus distribution subversion repository
+
+Once the staging repository has been released, the Apache Camel Quarkus
distribution subversion repository should be updated as sketched below.
+
+First, checkout the Apache Camel Quarkus distribution subversion repository:
+[source,shell]
+----
+$ svn co 'https://dist.apache.org/repos/dist/release/camel' camel-releases-dist
+----
+Add your public key to the file named `KEYS` if not already done.
+
+Assemble the Apache Camel Quarkus distribution:
+[source,shell]
+----
+$ mkdir -p "camel-quarkus/$VERSION"
+$ cd "camel-quarkus/$VERSION"
+$ export
URL='https://repository.apache.org/content/repositories/releases/org/apache/camel/quarkus/camel-quarkus'
+$ wget -O "apache-camel-quarkus-$VERSION-src.zip"
"$URL/$VERSION/camel-quarkus-$VERSION-src.zip"
+$ wget -O "apache-camel-quarkus-$VERSION-src.zip.asc"
"$URL/$VERSION/camel-quarkus-$VERSION-src.zip.asc"
+$ sha512sum "apache-camel-quarkus-$VERSION-src.zip" >
"apache-camel-quarkus-$VERSION-src.zip.sha512"
+----
+Ensure that only the latest release from each maintained branches is present.
+Typically, when releasing e.g. 1.4.0, you may need to delete e.g. 1.3.0:
+
+[source,shell]
+----
+$ cd .. && ls
+$ rm -fr 1.3.0
+----
+Review the changes:
+[source,shell]
+----
+$ svn diff
+----
+Commit the changes:
+[source,shell]
+----
+$ svn commit -m "Apache Camel Quarkus $VERSION released artifacts."
+----
+
== Further steps
In addition to the above, the following is needed:
