luigidemasi opened a new issue, #125: URL: https://github.com/apache/camel-kit/issues/125
The release automation still publishes the way the project did before the donation, and that is not an Apache release. **Current state** - `.github/workflows/release.yml` runs `.github/workflows/release.sh`, which executes `./mvnw -B -Psourcecheck,release,linux-ship-certification ... clean deploy`. - The `release` profile in `pom.xml` configures `central-publishing-maven-plugin` with `autoPublish=true` and `waitUntil=published`, so a run deploys straight to Maven Central. - `docs/releasing.md` describes this flow: prepare the version, tag, run the workflow, create the GitHub release. Nothing stages a release candidate and nothing waits for a vote. **What an Apache release needs** The [ASF release policy](https://www.apache.org/legal/release-policy.html#release-approval) requires a release candidate that the PMC can verify, a vote on the project mailing list, and at least three binding +1 votes before publication. The [Camel release guide](https://camel.apache.org/manual/release-guide.html) describes the staging, verification and vote sequence used by the Camel subprojects. **Expected work** 1. Change the release profile so a release run stages artifacts (no automatic publication) and promotion happens only after the vote. 2. Define the candidate convention (tag naming, source archive with checksums and signatures, where the candidate is staged, how it is announced on [email protected]). 3. Rewrite `docs/releasing.md` for the staging, vote and promotion sequence, and align the published documentation page on contributing and releasing, which currently labels the existing workflow as the pre-donation procedure. 4. Keep the preparation mechanics that still apply: `distribution.properties` as the source of version pins, the Knowledge MCP pin, the JBang launcher synchronization goal, the signed release build and tag. Release 0.4.1 predates the donation and is unaffected. The first release from `apache/camel-kit` must not be cut with the current workflow. Website impact: not required beyond the documentation page already written for it. -- 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]
