bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Mahé (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (BIGTOP-303) Rename Bigtop packages to reflect TLP status of packaged projects
Date Sat, 10 Dec 2011 20:42:44 GMT

    [ https://issues.apache.org/jira/browse/BIGTOP-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166973#comment-13166973
] 

Bruno Mahé commented on BIGTOP-303:
-----------------------------------

+1 on the rename

+1 On Apache Bigtop helping Apache Hadoop itself to have better separation between its different
parts. But this is not something Apache Bigtop can tackle itself. Patches would have to be
made upstream as well as convince upstream.of that benefit
I would rather separate this issue into another ticket so the issue of renaming projects to
reflect their TLP status could be tackled by non-commiter looking for an easy ticket to start
with.

                
> Rename Bigtop packages to reflect TLP status of packaged projects
> -----------------------------------------------------------------
>
>                 Key: BIGTOP-303
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-303
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: General
>    Affects Versions: 0.2.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.3.0
>
>
> All of the projects packaged by Bigtop have had TLP status for quite some time. It would
be nice to reflect that in the package names. Here's what needs to be renamed:
>    hadoop-0.20            -> hadoop
>    hadoop-hbase         -> hbase
>    hadoop-zookeeper -> zookeeper
>    hadoop-hive            -> hive
>    hadoop-pig              -> pig
> Please chime in on ramifications of this rename. My cursory check on http://pkgs.org
didn't reveal any naming conflicts with the proposed package names.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message