|
| 1 | +# Release |
| 2 | +Only [@jaredpetersen](https://github.com/jaredpetersen) is able to deploy a new release of Kafka Connect ArangoDB. Always deploy a new version to Maven Central and Confluent Hub. |
| 3 | + |
| 4 | +## GitHub |
| 5 | +1. Ensure that Kafka Connect ArangoDB's version was revised in the last merge to the master branch. |
| 6 | +2. Go to the [Releases section](https://github.com/jaredpetersen/kafka-connect-arangodb/releases) of the repository on GitHub. |
| 7 | +3. Draft a new release |
| 8 | +4. Fill the tag version input box with the new release version. |
| 9 | +5. Fill the release title input box with the new release version. |
| 10 | +6. Fill in the release description input bux with the recent changes using the [Keep a Changelog standard](https://keepachangelog.com/en/1.0.0/). |
| 11 | +7. Click the Publish release button. |
| 12 | + |
| 13 | +## Maven Central |
| 14 | +1. Ensure that Kafka Connect ArangoDB's version was revised in the last merge to the master branch. |
| 15 | +2. Deploy the plugin to Maven Central for staging. |
| 16 | + ``` |
| 17 | + mvn clean deploy -Pdeploy |
| 18 | + ``` |
| 19 | +3. Log in to the [repository manager](https://oss.sonatype.org/) for Maven Central. |
| 20 | +4. Navigate to [Staging Repositories](https://oss.sonatype.org/#stagingRepositories) and locate the staged release in the listings. |
| 21 | +5. Click on the staged release and navigate to the Content tab. |
| 22 | +6. Confirm that the content is correct. As an additional measure, you can download the published jar and confirm that the JAR works in the [local development cluster](/docs/development). |
| 23 | +7. If the content is correct, close the release by clicking the Close button at the top. |
| 24 | +8. The repository manager will begin evaluating the releasability of the plugin against the [Maven Central requirements](https://central.sonatype.org/pages/requirements.html). Assuming that everything is good to go, release the plugin by clicking the Release button at the top. |
| 25 | +9. Drop the staged repository by clicking the Drop button at the top. |
| 26 | +10. Wait at least an hour and [confirm that the plugin has been updated](https://search.maven.org/search?q=g:io.github.jaredpetersen%20AND%20a:kafka-connect-arangodb&core=gav). |
| 27 | +
|
| 28 | +## Confluent Hub |
| 29 | +1. Ensure that Kafka Connect ArangoDB's version was revised in the last merge to the master branch. |
| 30 | +2. Package the plugin in Confluent Hub's archive format. |
| 31 | + ``` |
| 32 | + mvn clean package |
| 33 | + ``` |
| 34 | +3. Send an email to [[email protected]](mailto:[email protected]?Subject=Kafka%20Connect%20ArangoDB%20Plugin%20--%20New%20Version%20Submission) attached with the compressed component archive located at `/target/components/packages`. If the component archive is too large, upload it to a cloud storage provider and provide the link. |
0 commit comments