I think we can do the Docker image separately. The way other projects seem to do it is that it is not an official release artifact that gets voted on, but is instead something that is created after the fact by an automated job. Let's continue the discussion in the 'docker build' thread.
Gian On Sat, Mar 16, 2019 at 7:32 AM Don Bowman <d...@agilicus.com> wrote: > On Fri, 15 Mar 2019 at 21:26, Jonathan Wei <jon...@apache.org> wrote: > > > Hi all, > > > > I have created a build for Apache Druid (incubating) 0.14.0, release > > candidate 1. > > > > Thanks to everyone who has contributed to this release! You can read the > > proposed release notes here: > > https://github.com/apache/incubator-druid/issues/7126 > > > > The release candidate has been tagged in GitHub as > > druid-0.14.0-incubating-rc1 (88ef108), available here: > > > > > https://github.com/apache/incubator-druid/releases/tag/druid-0.14.0-incubating-rc1 > > > > > > > Although its a bit late now, I am hoping that we make the docker image a > standard artifact. This really helps adoption. > The dockerfile is now in .14, but I didn't really see how that translates > into 'built in the pipeline as an artifact' > like other projects do. > > Any comment on what i can do to help this? after the PR was accepted etc, > it kind of vanished. >
