'Stable API' tag

I've added a "Stable API" tag on Github, to tag issues that should be either resolved or closed before Druid turns to 1.0 (stable API) version.

Re: [druid-dev] Apache migration logistics

Could archives of druid-dev and druid-users mailing lists be transferred to the new lists? On Thu, Mar 8, 2018 at 8:48 AM, Julian Hyde wrote: > I’m working on it. It turns that I don’t have sufficient karma to create a > git repo, so I’ve put in a request on the incubator list. > > > On Mar 6, 2

Re: [druid-dev] Apache migration logistics

I don’t know. I don’t think it’s easy. > On Mar 9, 2018, at 7:31 AM, Roman Leventov > wrote: > > Could archives of druid-dev and druid-users mailing lists be transferred to > the new lists? > > On Thu, Mar 8, 2018 at 8:48 AM, Julian Hyde > wrote: > I’m working on it.

Re: [druid-dev] Apache migration logistics

We can register dev@druid.apache.org and us...@druid.apache.org as a user in druid user groups so that going forward any mails that are sent to druid google groups are also received on the apache lists and is on the record. This would be to bridge the gap during the migration only. @Julian, I go a

Re: [druid-dev] Apache migration logistics

This thread is already going to both lists, and it looks like responses automatically go to both. Would be good to check what happens if we subscribe dev@ to the google group. If responding from the apache list doesn't automatically add the google group as well, it will be hard to keep the group us