The geode kafka connector currently has a separate release cycle compared to the main Geode project. There are instructions to manually create a release of the kafka connector.

Steps


1. Checkout the kafka connector at the appropriate point and build it. This assumes you have already created a support branch you intend to release from, eg support/1.2

git clone git@github.com:apache/geode-kafka-connector.gitgit checkout support/1.2tar --exclude-vcs -zcvf geode-kafka-connector-src.tgz ./geode-kafka-connectorcd geode-kafka-connector
mvn package


2. Checkout the apache SVN repository that is used to store release artifacts

mkdir svn_staging 
cd svn_staging/ 
svn checkout https://dist.apache.org/repos/dist --depth empty  
svn update --set-depth immediates --parents dist/release/geode  
svn update --set-depth infinity --parents dist/dev/geode


3. Copy the artifacts to the dev directory for staging

mkdir dist/dev/geode/kafka-connector-1.1.0
cp geode-kafka-connector-src.tgz dist/dev/geode/kafka-connector-1.1.0
cp cp geode-kafka-connector/target/components/packages/apache-kafka-connect-geode-1.1.0.zip dist/dev/geode/kafka-connector-1.1.0


4. Manually sign the generated artifacts with your GPG key and create SHA256 sums. You must be using a gpg key that is listed in the KEYS file of the apache geode distribution, on your profile on id.apache.org, and ideally signed by multiple other committers.


cd  dist/dev/geode/kafka-connector-1.1.0 
gpg --armor --output  geode-kafka-connector-src.tgz .asc --detach-sig  geode-kafka-connector-src.tgzsha256sum  geode-kafka-connector-src.tgz  >  geode-kafka-connector-src.tgz.sha256

gpg --armor --output apache-kafka-connect-geode-1.1.0.zip.asc --detach-sigapache-kafka-connect-geode-1.1.0.zip
sha256sum  apache-kafka-connect-geode-1.1.0.zip  >  apache-kafka-connect-geode-1.1.0.zip.sha256



5. Commit the artifacts to svn to publish the release candidate

svn add  dist/dev/geode/kafka-connector-1.1.0  
svn commit


3. Tag the release candidate

cd geode-kafka-connector
git tag rel/v1.1.0.RC1



3. Send out a VOTE email to dev@geode.apache.org. It should be open for at least 72 hours. See the mailing list history for previous examples. You must get at least 3 +1 votes from PMC members.

4. Once the VOTE is closed, send a summary to dev@geode.apache.org.

5. Move the artifacts to the release directory

6. Tag the release

7. Update the geode-site page with pointers to the release artifacts

8. Wait until the artifacts are available on the apache CDN

9. Send an email to the apache announce list describing the release and pointing to the geode download page

10. Create a github release from the final tag

11. Publish the connector to the confluent hub by emailing the confluent hub maintainers.

  • No labels