[
https://issues.apache.org/jira/browse/HADOOP-12361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737501#comment-14737501
]
Sean Busbey commented on HADOOP-12361:
--------------------------------------
I think we could do this:
# set up a precommit job that looks for subtasks of HADOOP-12111 (and/or
component yetus)
# send everything that matches to a job set up just for yetus with --project
yetus (and either --branch-default HADOOP-12111 or make a personality)
# send everything else to a job that's a copy of the current Hadoop Common
precommit (wether it runs off of the yetus branch or not)
bq. (This could be an argument that test-patch should allow for the personality
to specify which branches get which build systems, but ugh. That seems overkill
esp for an event that rarely happens in most source trees.)
One advantage of this approach is that we'd be in a position to handle projects
that use gh-pages or hte ASF git based website system.
> reorganize repo layout for break from Hadoop code base
> ------------------------------------------------------
>
> Key: HADOOP-12361
> URL: https://issues.apache.org/jira/browse/HADOOP-12361
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: yetus
> Affects Versions: HADOOP-12111
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Attachments: HADOOP-12361.HADOOP-12111.1.sh
>
>
> Reorganize current top level repo to include our starting modules (and only
> those modules), so that it's easier to start bringing in new contributors:
> * shelldoc
> * releasedocmaker
> * interface audience
> * test-patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
