Re: deprecating the old repo

2019-04-27 Thread Jokin Cuadrado
Ok, I will take a look on it on monday. Regards. On Fri, Apr 26, 2019 at 8:02 PM Gian Merlino wrote: > That makes sense to me. Are you interested in doing a PR to the > docker-druid repo to make its README point to the new Dockerfiles? If so, > that should do it. > > On Fri, Apr 26, 2019 at

Re: deprecating the old repo

2019-04-26 Thread Eyal Yurman
I think after this final pr, is will be proper to archive the repository so it doesn't look active ( https://help.github.com/en/articles/archiving-a-github-repository). It will be accessible, but read-only, and won't come up in the default GitHub search. Here's an example for such a repository

Re: deprecating the old repo

2019-04-26 Thread Julian Hyde
One trick that people sometimes use is to create a new branch called “obsolete” or similar, update the README in that branch to point to the new project location, and make that branch the default branch in GitHub. > On Apr 26, 2019, at 11:02 AM, Gian Merlino wrote: > > That makes sense to me.

Re: deprecating the old repo

2019-04-26 Thread Gian Merlino
That makes sense to me. Are you interested in doing a PR to the docker-druid repo to make its README point to the new Dockerfiles? If so, that should do it. On Fri, Apr 26, 2019 at 3:33 AM Jokin Cuadrado wrote: > Hi, I was searching for a way to run druid on docker for some > experimentation,

deprecating the old repo

2019-04-26 Thread Jokin Cuadrado
Hi, I was searching for a way to run druid on docker for some experimentation, and the first results has been a repo on the droid-io organization https://github.com/druid-io/docker-druid I found after (Thanks to dylan pointing out in slack) that there are newer dockerfiles commited on the apache