We should probably have a label for it too.
On Thu, May 31, 2018 at 9:23 AM, Gian Merlino wrote:
> I don't see why not!
>
> On Thu, May 31, 2018 at 9:21 AM, Charles Allen wrote:
>
>> Sounds good. I'd like to put some more formal tracking and responsibility
>> to the remaining incubator items. W
I don't see why not!
On Thu, May 31, 2018 at 9:21 AM, Charles Allen wrote:
> Sounds good. I'd like to put some more formal tracking and responsibility
> to the remaining incubator items. Would github issues be the preferred
> place to do that?
>
> On Thu, May 31, 2018 at 9:20 AM Gian Merlino
>
Sounds good. I'd like to put some more formal tracking and responsibility
to the remaining incubator items. Would github issues be the preferred
place to do that?
On Thu, May 31, 2018 at 9:20 AM Gian Merlino wrote:
> I think we are planning to keep using GitHub issues, based on the
> discussion
I think we are planning to keep using GitHub issues, based on the
discussion in the migration logistics thread. And based on the fact that
Apache seems to allow that now (https://github.com/apache/fluo was given as
an example). So probably the right thing to do is update
http://incubator.apache.org
Hi all
http://incubator.apache.org/projects/druid.html says that
https://issues.apache.org/jira/browse/DRUID is our issue tracker, but I
don't seem to have access to it. Does anyone know how to apply for access
using an existing Apache JIRA login?
Thanks,
Charles Allen
