You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@impala.apache.org by Henry Robinson <he...@apache.org> on 2016/03/23 00:32:14 UTC

JIRAs tracking infrastructure move to ASF

Hi all -

Just wanted to draw everyone's attention to the following JIRA and its
subtasks:

https://issues.cloudera.org/browse/IMPALA-3221

These track the required steps for us to move Impala development from
Cloudera infrastructure over to the ASF. There's quite a bit of work to do
to ensure that Impala is accessible for new contributors while established
contributors remain productive. Rather than do all this work internally and
make it look like there's no progress, I wanted to surface all the tasks on
JIRA so that everyone can see how things are moving.

Cheers,
Henry

Re: JIRAs tracking infrastructure move to ASF

Posted by Henry Robinson <he...@cloudera.com>.

Good idea to track it! Suggest you have a separate umbrella JIRA so as not
to make make the whole think more unwieldy than it needs to be, as the docs
move can progress independently IIUC.

On 23 March 2016 at 08:53, John Russell <jr...@cloudera.com> wrote:

> Why don't I add corresponding doc-related subtasks under here, because the
> same exercise of pushing initial source files and setting up a build
> process applies on the doc side as well.
>
> Thanks,
> John
>
> > On Mar 22, 2016, at 4:32 PM, Henry Robinson <he...@apache.org> wrote:
> >
> > Hi all -
> >
> > Just wanted to draw everyone's attention to the following JIRA and its
> > subtasks:
> >
> > https://issues.cloudera.org/browse/IMPALA-3221
> >
> > These track the required steps for us to move Impala development from
> > Cloudera infrastructure over to the ASF. There's quite a bit of work to
> do
> > to ensure that Impala is accessible for new contributors while
> established
> > contributors remain productive. Rather than do all this work internally
> and
> > make it look like there's no progress, I wanted to surface all the tasks
> on
> > JIRA so that everyone can see how things are moving.
> >
> > Cheers,
> > Henry
>
>


-- 
Henry Robinson
Software Engineer
Cloudera
415-994-6679

Re: JIRAs tracking infrastructure move to ASF

Posted by John Russell <jr...@cloudera.com>.

Why don't I add corresponding doc-related subtasks under here, because the same exercise of pushing initial source files and setting up a build process applies on the doc side as well.

Thanks,
John

> On Mar 22, 2016, at 4:32 PM, Henry Robinson <he...@apache.org> wrote:
> 
> Hi all -
> 
> Just wanted to draw everyone's attention to the following JIRA and its
> subtasks:
> 
> https://issues.cloudera.org/browse/IMPALA-3221
> 
> These track the required steps for us to move Impala development from
> Cloudera infrastructure over to the ASF. There's quite a bit of work to do
> to ensure that Impala is accessible for new contributors while established
> contributors remain productive. Rather than do all this work internally and
> make it look like there's no progress, I wanted to surface all the tasks on
> JIRA so that everyone can see how things are moving.
> 
> Cheers,
> Henry

Re: JIRAs tracking infrastructure move to ASF

Posted by Tom White <to...@cloudera.com>.

Thanks Henry!

On Tue, Mar 22, 2016 at 11:32 PM, Henry Robinson <he...@apache.org> wrote:
> Hi all -
>
> Just wanted to draw everyone's attention to the following JIRA and its
> subtasks:
>
> https://issues.cloudera.org/browse/IMPALA-3221
>
> These track the required steps for us to move Impala development from
> Cloudera infrastructure over to the ASF. There's quite a bit of work to do
> to ensure that Impala is accessible for new contributors while established
> contributors remain productive. Rather than do all this work internally and
> make it look like there's no progress, I wanted to surface all the tasks on
> JIRA so that everyone can see how things are moving.
>
> Cheers,
> Henry