Hi Remember that Apache requires to release source artifact on dist.Apache.org. Binaries should go also on dist and wherever we want.
But we have to update the process to push source artifact on dist. And a release has some requirements: disclaimer, notice, license. I think we are not yet ready for a release. Even the code base is not ready from a Apache standpoint. Before rushing on a release, please work with me and other mentors on process and code base. Thanks Regards JB Le sam. 30 avr. 2022 à 16:52, tison <[email protected]> a écrit : > Hi Kvrockers, > > One of our major target in the following months and also a strict > requirement to graduate from > the Incubator is making an Apache release. > > I can see that, currently, we release the source code via GitHub > Release[1], along with binary > installer .deb and .rpm file. Also, there is a DockerHub register we > release docker image[2]. > So far, we release these artifacts with a GitHub Actions[3]. > > I'd like to gather information from the contributors to see a full list of > all artifact to be released, > and start the discussion about how we release (deliver) those artifacts in > the following era, in > the Apache way. > > Best, > tison. > > [1] https://github.com/apache/incubator-kvrocks/releases > [2] https://hub.docker.com/r/kvrocks/kvrocks > [3] > > https://github.com/apache/incubator-kvrocks/blob/77f7c6f53c6b747977285357fc94ec4af0d862eb/.github/workflows/release.yaml >
