For 0.8 release, I did some work and I wanted to share the latest status. I think we should target for *docker-image-based* release mode. I propose to release a unified open-source tarball, we don't release a binary tarball (not a must [1]). Things have been *DONE*:
1. I have created a repo for release mgmt: https://github.com/yangwwei/yunikorn-release, I think we need to move this to apache repo too. 2. This repo has the instructions and tools for a release. The tool loads configs from https://github.com/yangwwei/yunikorn-release/blob/master/tools/release-configs.json and downloads source code from certain repo/branch/hash to assemble the release artifacts 3. This repo contains a *build-docker-image.sh* to build yunikorn docker images (scheduler, admission-controller, and web) 4. I have created *branch-0.8* for all 4 repos 5. The generated tarball will also have the helm chart for user to install and run yunikorn on an existing K8s cluster 6. I tried to generate PGP key and sign the tarball Things *TODO* 1. Create a repo for yunikorn-release under ASF 2. IIUC, https://issues.apache.org/jira/browse/YUNIKORN-79 is a blocker for 0.8. Can we get this fixed ASAP? 3. Once #2 is done, create a tag for 0.8-rc1 and start the voting thread Thanks! [1] https://infra.apache.org/release-publishing.html *The Apache Software Foundation exists to create open source software, so the fundamental requirement for a release is that it has the necessary source code to build the project. A project may provide compiled binaries of each release for the convenience of users.*
