Apache Camel Kafka Connect release process
The process is mutatis mutandis the same as for the main Apache Camel repository - see the Release guide page of the Camel documentation.
Close the GitHub release milestone and assign any remaining issues that aren’t covered by the release to the next milestone
Be sure you switch to a branch to perform the release, do not release from
main branch unless you have a specific reason and you know what you are doing:
$ git checkout -b <branch_name>
| A good branch name is in the form |
You can do a dry run to be sure all is ok:
$ ./mvnw release:prepare -DdryRun -Prelease -DreleaseVersion=<the_version_you_want_to_release> -DdevelopmentVersion=<the_next_snapshot_version>
if you performed a dray run please clean up the release before continuing:
$ ./mvnw release:clean
Prepare the release:
./mvnw -Prelease -DreleaseVersion=<the_version_you_want_to_release> -DdevelopmentVersion=<the_next_snapshot_version> -Dtag=<tag_name> -Dusername=<your_apache_username> -Dpassword=<your_apache_password> release:prepare
Add and commit all the updated json with a commit comment on the line of
"[after release perform chore]: regen catalog descriptors with new version" then update the tag
<tag_name> to point to the just created commit and push it upstream (you may need to delate the original tag
<tag_name> created during the
release:prepare step above):
$ git add *.json $ git stash $ git checkout <tag_name> $ git stash pop $ git add *.json $ git commit -m"[after release perform chore]: regen catalog descriptors with new version" $ git tag -f <tag_name> $ git push -f upstream <tag_name> $ git checkout <branch_name>
Upload your artifacts on apache nexus maven server:
$ ./mvnw -Prelease -Dusername=<your_apache_username> -Dpassword=<your_apache_password> release:perform
$ mvn clean release:clean release:prepare -DreleaseVersion=$VERSION -DdevelopmentVersion=$NEXT_VERSION -B release:perform
In case 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-splunk-kafka-connector, a resume attempt could be triggered as below:
$ cd target/checkout $ ./mvnw -Prelease -Dusername=<your_apache_username> -Dpassword=<your_apache_password> deploy -rf :camel-splunk-kafka-connector
select the open repository (the name usually contains a number)
There will be some checks done by nexus, wiat tho see that they complete successfully.
Send an email to email@example.com with object:
[VOTE] Release Camel-Kafka-connector <the_version_you_want_to_release> you can select 48 or 72 hours for the vote. The message can be something like:
Hello all, This is a vote to release Apache Camel-kafka-connector X Staging repository: https://repository.apache.org/content/repositories/orgapachecamel-Y Tag: https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-X <some release comments here> Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel-kafka-connector X [ ] -1 Veto the release (provide specific comments) The vote is open for at least <48 | 72> hours. Thanks.
X is the release you are performing and
Y is the staging repository number created during release.
This may require a rebase of
main branch on the release branch if some commits have been added to
main after you created the release branch (in that case you can perform a
push -f on
Once the vote time has passed send another email with object:
[RESULT][VOTE] Release Camel-Kafka-connector <the_version_you_want_to_release> with the count of binding and not binding votes. The message can be something like:
Hi all, This vote passes with the following result Y +1 binding votes (<names of binding votes>) Z +1 non-binding (<names of non binding votes>) Thanks to everybody. I'll publish the artifacts in a bit. Regards.
select the closed repository
Upload the files:
to apache dist svn:
$ cd distribution/target $ mkdir releases $ cp camel-kafka-connector-<the_version_you_released>-src.zip camel-kafka-connector-<the_version_you_released>-src.zip.asc camel-kafka-connector-<the_version_you_released>-src.zip.sha512 releses/ $ svn import release/ https://dist.apache.org/repos/dist/release/camel/camel-kafka-connector/<the_version_you_released> -m"Camel Kafka Connector <the_version_you_released> import."
Create a release note in https://github.com/apache/camel-website/tree/master/content/releases/ckc by coping and changing one of the already present.
Update last released version:
<configuration> <lastReleasedVersion>0.7.0</lastReleasedVersion> </configuration>
connectors/pom.xml and regen.
Since we use github but behind the scene the git repository is kept in sync with the Apache gitbox mirror, but the
release:perform maven goal checkout from gitbox server, there might be some sync issues. Those usually come in the form on error complaining about tags or branches already present. To delete the not in sync offending tag or branches from gitbox:
$ git push 'https://<your_apache_username>:<your_apache_password>@gitbox.apache.org/repos/asf/camel-kafka-connector.git' :refs/tags/<tag_name> $ git push -f 'https://<your_apache_username>:<your_apache_password>@gitbox.apache.org/repos/asf/camel-kafka-connector.git' <branch_name>