zbendhiba opened a new issue #3350: URL: https://github.com/apache/camel-quarkus/issues/3350
Hello, I've had done some additional steps, regarding what we have in the release guide here : https://camel.apache.org/camel-quarkus/next/contributor-guide/release-guide.html And this is how I'd love to update the release guide : - When we generate the 2.6.x branch. Before pushing the branch, we need to update the antora version, but also scripts (as we push a snapshot version. See this commit as a reference : https://github.com/apache/camel-quarkus/pull/3339/commits/d4357cf7ce9c451b66654e77b50f0b8a0d78f388 I wonder if we could automate this, using maven. Let me know - When [we update the subversion repository](https://camel.apache.org/camel-quarkus/next/contributor-guide/release-guide.html#_update_the_apache_camel_quarkus_distribution_subversion_repository.), we delete the latest version, before announcing the new one in the camel website : For some time, the [download page ](https://camel.apache.org/download/#camel-quarkus)doesn't work. I'd advise we keep the 2 latest versions. It could make the download page happy + Camel K is not updated yet + https://code.quarkus.io/ presents the 2 latest versions. Would love to have some feedback on this. - When we add the release on the website, we must add the new version on the website too. See commit here: https://github.com/apache/camel-website/pull/691/commits/b458d786d725dacc24a7d1e7bb97434e7a1c3042 I'd advise also to just keep 2 latest versions, for same reason as precedent point. - Review the paragraph of [updating camel-quarkus-examples ](https://camel.apache.org/camel-quarkus/next/contributor-guide/release-guide.html#_upgrade_and_tag_examples). The PR must have the next version, and not the next version of snapshot. Maybe do as for the release a push of the tag and release branch ? There is a direct push to main that must be reviewed. I can propose a PR for this update - [ update the quarkus platform](https://camel.apache.org/camel-quarkus/next/contributor-guide/release-guide.html#_upgrade_camel_quarkus_in_quarkus_platform) : use their maven wrapper, as I had an issue with my new maven version, getting more than 100+ files updated, due to style difference. Using the `./mvnw` instead made the PR better. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
