Re: [DISCUSS] Sorting out release artifact

[hulk <hu...@gmail.com>]

Hi tison

Your list is all artifacts that we have released.

Thanks tison and JB.

On Sun, May 1, 2022 at 2:06 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:

> Hi tison
>
> You do right ! Let’s work together on preparation.
>
> Thanks
> Regards
> JB
>
> Le sam. 30 avr. 2022 à 19:01, tison <wa...@gmail.com> a écrit :
>
> > Hi hulk,
> >
> > I'd like to know, aside from the artifactss listed above - source code
> and
> > installer via gh release, docker hub images - is there other artifact you
> > ever released.
> >
> > Hi JB,
> >
> > I don't want to rush for a release in weeks. Instead, basing an Apache
> > project produces open-source software, releasing is a good milestone we
> can
> > work for.
> >
> > Actually I start this thread to listen to you about inputs on the release
> > process, which we would have a rough consensus, writing down and vote.
> >
> > The disclaimer and such progress docs could be resolved with a website
> and
> > we may start another thread on the website topic.
> >
> > For "codebase is not ready from an Apache standpoint", could you
> elaborate
> > a bit more?
> >
> > Best,
> > tison.
> >
> >
> >
> > Jean-Baptiste Onofré <jb...@nanthrax.net>于2022年5月1日 周日00:07写道：
> >
> > > 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 <wa...@gmail.com> 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
> > > >
> > >
> > --
> > Best,
> > tison.
> >
>


-- 
Best Regards,
- *Hulk Lin*