You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2015/01/16 20:02:35 UTC
[jira] [Comment Edited] (BIGTOP-1604) Create a MAINTAINERS.txt File
[ https://issues.apache.org/jira/browse/BIGTOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280664#comment-14280664 ]
jay vyas edited comment on BIGTOP-1604 at 1/16/15 7:02 PM:
-----------------------------------------------------------
For me: packaging around spark, tachyon, BigPetStore, all the gradle based smoke-tests, vagrant recipes.
was (Author: jayunit100):
Foe me: packaging around spark, tachyon, BigPetStore, all the gradle based smoke-tests, vagrant recipes.
> Create a MAINTAINERS.txt File
> -----------------------------
>
> Key: BIGTOP-1604
> URL: https://issues.apache.org/jira/browse/BIGTOP-1604
> Project: Bigtop
> Issue Type: Bug
> Components: general
> Affects Versions: 0.9.0
> Reporter: jay vyas
> Priority: Critical
>
> Start with 0.9, lets maintain a MAINTAINERS.txt file which has component, maintainer names.
> Everybody *please* add entries here for components in bigtop that you will maintain.
> I think we Are we in agreement that,
> - Components that *ARE NOT* in this file, can be dropped without much debate. No point in releasing something that is maintained by pure chance of randomly someone deciding to add a patch.
> - Components that *ARE* added in this file will, for obvious reasons, be central to the architecture of the bigtop distribution.
> Componnets are : YARN, HBASE, SPARK, HIVE, PIG, MAHOUT, FLUME, (many others ...) folks please chime in on what you can maintain in the comments below, and I'll craft the file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)