impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Brown (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-3398) Move Impala documentation development to ASF
Date Wed, 19 Apr 2017 16:58:41 GMT

     [ https://issues.apache.org/jira/browse/IMPALA-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Brown resolved IMPALA-3398.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.9.0

All the dependent Jira issues are fixed.

> Move Impala documentation development to ASF
> --------------------------------------------
>
>                 Key: IMPALA-3398
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3398
>             Project: IMPALA
>          Issue Type: Task
>          Components: Infrastructure
>    Affects Versions: Impala 2.5.0
>            Reporter: John Russell
>            Assignee: John Russell
>            Priority: Minor
>              Labels: asf
>             Fix For: Impala 2.9.0
>
>
> This JIRA is an umbrella for all the tasks we have to complete to transition Impala documentation
work from Cloudera's infrastructure to the ASF. The end goals are:
> # All Impala documentation is in the ASF's git repository
> # Cloudera's Impala documentation team develops against the ASF repository, using ASF
infrastructure where possible (JIRA etc.)
> # New contributors can build and view Impala docs easily without access to Cloudera infrastructure
> # Disentangle documentation topics that include Cloudera-only subjects, e.g. using Impala
with Cloudera Manager
> # Make the documentation source reusable that Impala content does not have to be removed
from existing locations, which would be a disruptive experience for users



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message