components are involved a new HADOOPX- referring to such
earlier Jira?
Cheers,
Joep
From: Todd Lipcon [t...@cloudera.com]
Sent: Monday, June 13, 2011 1:37 PM
To: general@hadoop.apache.org
Subject: Re: JIRAs post-unsplit
On Mon, Jun 13, 2011 at 11:51 AM
to
such earlier Jira?
Cheers,
Joep
From: Todd Lipcon [t...@cloudera.com]
Sent: Monday, June 13, 2011 1:37 PM
To: general@hadoop.apache.org
Subject: Re: JIRAs post-unsplit
On Mon, Jun 13, 2011 at 11:51 AM, Konstantin Boudnik c...@apache.org
wrote:
I
I tend to agree: JIRA separation was the benefit of the split.
I'd rather keep the current JIRA split in effect (e.g. separate JIRA projects
for separate Hadoop components; don't recombine them) and file patches in the
same way (for common, hdfs, mapreduce). If a cross component patch is needed
On Mon, Jun 13, 2011 at 01:37PM, Todd Lipcon wrote:
On Mon, Jun 13, 2011 at 11:51 AM, Konstantin Boudnik c...@apache.org wrote:
I tend to agree: JIRA separation was the benefit of the split.
I'd rather keep the current JIRA split in effect (e.g. separate JIRA
projects
for separate
On Mon, Jun 13, 2011 at 4:54 PM, Konstantin Boudnik c...@apache.org wrote:
On Mon, Jun 13, 2011 at 01:37PM, Todd Lipcon wrote:
On Mon, Jun 13, 2011 at 11:51 AM, Konstantin Boudnik c...@apache.org
wrote:
I tend to agree: JIRA separation was the benefit of the split.
I'd rather keep
