bobbai00 opened a new issue, #4218:
URL: https://github.com/apache/texera/issues/4218

   ### Feature Summary
   
   The current release process only produces a source tarball. Per Apache 
release policy, the release should contain everything a new user needs to get 
started, including deployment descriptors that reference auditable container 
images.
   
   Following the [Apache Flink Kubernetes Operator release 
model](https://dist.apache.org/repos/dist/release/flink/flink-kubernetes-operator-1.14.0/),
 the release should include signed binary artifacts alongside the source 
tarball.
   
   ### Proposed Solution or Design
   
   Add two binary release artifacts (GPG-signed + SHA512 checksummed) to the 
release candidate:
   
   1. **Docker Compose deployment bundle** 
(`apache-texera-VERSION-docker-compose.tar.gz`)
      - Contains `docker-compose.yml`, `.env` (pinned to release version), 
`nginx.conf`, and `sql/` init scripts
      - Self-contained: users extract and run `docker compose up -d`
   
   2. **Helm chart package** (`apache-texera-VERSION-helm.tgz`)
      - Packaged via `helm package` with release version in `Chart.yaml`
   
   Additionally:
   - Parameterize image references in `docker-compose.yml` and Helm 
`values.yaml` using `IMAGE_REGISTRY` / `IMAGE_TAG` variables (defaults to 
`ghcr.io/apache` / `latest` in main branch; pinned to release version in 
artifacts)
   - Update the `build-and-push-images` workflow to support both ghcr.io (via 
`GITHUB_TOKEN`) and Docker Hub
   - Update the `create-release-candidate` workflow to produce and upload all 
three artifacts
   - Update the vote email template to list container images and deployment 
verification checklist items
   
   **Release directory structure:**
   ```
   dist.apache.org/repos/dist/dev/incubator/texera/VERSION-RCN/
     apache-texera-VERSION-src.tar.gz          + .asc + .sha512
     apache-texera-VERSION-docker-compose.tar.gz + .asc + .sha512
     apache-texera-VERSION-helm.tgz            + .asc + .sha512
   ```
   
   Container images are published to ghcr.io as convenience binaries, built 
from the voted-on source. The Dockerfiles in the source tarball enable audit 
and verification.


-- 
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]

Reply via email to