Description

This issue tracks the steps to cut and approve the first Apache Software Foundation–compliant release of the Druid Operator. The goal is to publish a signed source release via ASF infrastructure, with corresponding convenience artifacts (Helm chart, Docker image) built from that release.

Background

ASF release policy requires signed source releases distributed via downloads.apache.org.
Helm charts and Docker images may be provided as convenience binaries, but they must be built from the approved source release.
A successful release requires a [VOTE] on [email protected] with at least 3 binding PMC +1 votes and a minimum of 72h voting window.

Tasks

Prepare release candidate

• Ensure repo has updated LICENSE, NOTICE, KEYS, DISCLAIMER-WIP (until first release approved)
• Tag RC: vX.Y.Z-rc1
• Build source tarball (druid-operator-X.Y.Z-src.tar.gz)
• Sign (.asc) and checksum (.sha512) artifacts
• Stage artifacts under dist/dev/druid/druid-operator/X.Y.Z-rc1/

Community review & vote

• Send [VOTE] email to [email protected] with artifact links, checksums, KEYS pointer
• Keep vote open for minimum 72h
• Collect at least 3 binding +1 votes (PMC members)
• Announce result with [RESULT] email

Promote approved release

• Move artifacts from dist/dev to dist/release
• Verify availability on Apache mirrors under downloads.apache.org/druid/druid-operator/
• Update website & docs with release notes
• Convenience binaries
• Package and publish Helm chart (.tgz + index.yaml) under ASF dist / project site
• Build and push Docker images to apache/druid-operator on Docker Hub (from release tag)
• Document installation (helm repo add / docker pull)

Acceptance Criteria

• Apache-compliant source release is available on downloads.apache.org/druid/druid-operator/X.Y.Z/
• Release has passed community vote with sufficient binding approvals
• Helm chart and Docker images are published as convenience binaries, clearly tied to the release tag
• Release notes and docs updated to reference the first Apache release