atom feed31 messages in org.apache.hadoop.generalRe: HADOOP-7106 (project unsplit) thi...
FromSent OnAttachments
Todd LipconJun 10, 2011 11:19 am 
Eli CollinsJun 10, 2011 11:34 am 
Owen O'MalleyJun 10, 2011 11:39 am 
Todd LipconJun 11, 2011 8:25 pm 
Todd LipconJun 12, 2011 2:50 pm 
Todd LipconJun 12, 2011 4:38 pm 
Eli CollinsJun 13, 2011 12:39 am 
Marcos OrtizJun 13, 2011 6:24 am 
Harsh JJun 13, 2011 6:31 am 
Marcos OrtizJun 13, 2011 6:42 am 
Robert EvansJun 13, 2011 6:58 am 
Robert EvansJun 13, 2011 7:04 am 
Todd LipconJun 13, 2011 7:51 am 
Todd LipconJun 13, 2011 7:57 am 
Jeffrey NaisbittJun 13, 2011 8:05 am 
Robert EvansJun 13, 2011 8:10 am 
Todd LipconJun 13, 2011 8:13 am 
Nigel DaleyJun 13, 2011 8:35 am 
Todd LipconJun 13, 2011 9:03 am 
Jeffrey NaisbittJun 13, 2011 9:24 am 
Todd LipconJun 13, 2011 10:01 am 
Alejandro AbdelnurJun 13, 2011 10:04 am 
Jeffrey NaisbittJun 13, 2011 10:08 am 
Tsz Wo (Nicholas), SzeJun 13, 2011 11:41 am 
Matthew FoleyJun 13, 2011 12:51 pm 
Todd LipconJun 13, 2011 1:35 pm 
Todd LipconJun 13, 2011 1:52 pm 
Todd LipconJun 13, 2011 6:48 pm 
Ian HolsmanJun 14, 2011 4:31 pm 
Ranjit MathewJun 16, 2011 2:26 am 
Todd LipconJun 16, 2011 9:01 am 
Subject:Re: HADOOP-7106 (project unsplit) this weekend
From:Todd Lipcon (to@cloudera.com)
Date:Jun 13, 2011 1:35:09 pm
List:org.apache.hadoop.general

On Mon, Jun 13, 2011 at 11:42 AM, Tsz Wo (Nicholas), Sze < s297@yahoo.com> wrote:

Todd,

Great work!

A few minor problems: (1) I had committed MAPREDUCE-2588, however, an commit email was sent to both common-commits@ and mapreduce-commits@. (2) hadoop/site becomes an empty directory. (3) There are svn properties in hadoop/common/trunk/

(2) and (3) are simple. I will remove hadoop/site and the svn properties for hadoop/common/trunk/.

Does anyone know how to fix (1)?

Ah, we need to update the mailer config. This is the remaining task I mentioned on the HADOOP-7106 JIRA. We had updated it to include both the old and new spots for the sake of the transition. I'll ping Ian about this - I think he's the only one with access.

A separated question: Strictly speaking, this is not "project unsplit" since we are going to submit patches for individual sub-projects as before, i.e. we keep generating and committing patches to common/trunk/[common/hdfs/mapreduce] but not common/trunk; hudson will pick up patches from individual sub-projects, etc. Am I correct? Just want to make sure that everyone is on the same page. :)

Correct, that's where we at for today. I opened HADOOP-7384 which will allow patches generated against the "full repo" to apply to an individual project, to make life easier for git users, but right now we still need separate JIRAs and patches. See my other thread from this morning about some ideas how we might be able to do cross-project patches in a reasonable way.

-Todd