Update release guide (#5790)
* Update release guide
* fixup
diff --git a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
index 0b3c48c..9b201ee 100644
--- a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
@@ -14,6 +14,7 @@
* When releasing after a recent Quarkus release, check for new releases of third party Quarkus extensions we depend on.
They are listed in the https://github.com/apache/camel-quarkus/blob/main/pom.xml#L48-L61[Primary dependencies] section of the top level `pom.xml`.
If there are new releases, upgrade the versions accordingly and run `mvn cq:sync-versions -N` from the root directory of the source tree.
+ Note that some of the versions are mandated by quarkus, so camel-quarkus should use the same values as the quarkus-platform bom.
* Close the GitHub release https://github.com/apache/camel-quarkus/milestones[milestone] and assign any remaining issues that aren't covered by the release to the next milestone
== Create a release branch
@@ -90,11 +91,15 @@
It's important that the machine running the `perf-regression` tool be equally loaded during the run.
The simplest way would be to take a 1 hour slot at the end of the day, launch the tool on your main station and then lock the screen.
+At this stage, one is probably working from the release branch.
+The performance regression tool might be present in the `target/checkout` folder.
+Otherwise a full `mvn clean install -Dquickly` rebuild is needed prior to running the performance regression tool.
+Another option is to switch to the main branch, where no rebuild should be needed.
+
For instance, running the tool to compare the `2.10.0` staging release against the `2.9.0` previous release would look as below:
[source,shell]
----
-$ cd tooling/perf-regression
$ java -jar target/quarkus-app/quarkus-run.jar -an 2.9.0 2.10.0
----
