This is purely a packaging exercise. I don't see a reason to mark this as experimental.
Rajiv. ________________________________ From: Dylan Wylie <dylanwy...@apache.org> Sent: Friday, February 8, 2019 6:08:47 AM To: dev@druid.apache.org Subject: Re: docker build I believe all we have to do is submit a ticket to Apache's Infrastructure team and then we'll have some automatic process that'll automatically update docker-hub with images relating to each release. I guess there's two open questions I think we should reach a consensus on (others feel free to add more!). - Are we as a community happy to "support" an additional release artefact? I'm happy to try to incorporate this into my employer's testing infrastructure to help catch any regressions on future releases but that's just one data point on each release. - Along the same vein, do we follow the same process as we do with new features and mark this as experimental for some time? On Fri, 8 Feb 2019 at 13:25, Don Bowman <d...@agilicus.com> wrote: > Now that > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-druid%2Fpull%2F6896&data=02%7C01%7Crmordani%40vmware.com%7C942b2af1dfb740fcbed308d68dcef937%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C636852317419449405&sdata=EXigZIBkKiatM0rEgyQRoxA9ER8u8amiAfPN0MghzjE%3D&reserved=0 > is merged > (thank you!) > > who can get this set to build into Dockerhub? Presumably automatically on a > 'tag' of the repo. > > Once that is done it is much more convenient for folks to use this tool. > > --don >
