Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update release guide #5790

Merged
merged 2 commits into from
Feb 22, 2024
Merged

Update release guide #5790

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4e0d4db
Update release guide
aldettinger Feb 22, 2024
1668786
fixup
aldettinger Feb 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ xref:manual::release-guide.adoc[Camel Release guide].
* 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
Expand Down Expand Up @@ -90,6 +91,10 @@ Once the staging repository has been closed, run the `perf-regression` tool in o
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.
From there, a full `mvn clean install -Dquickly` rebuild is needed prior to running the performance regression tool.
aldettinger marked this conversation as resolved.
Show resolved Hide resolved
It could be simpler 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]
Expand Down