I'm coming around on splitting up HDFS and Mapred etc. I'll reply to
that thread with a new shinny +1.
So that leaves me -1 on this proposal of splitting up the core/jira
traffic.
Nige
On Sep 5, 2008, at 2:50 PM, Doug Cutting wrote:
+0
We really need to split hadoop-core into two or more subprojects
Keeping HDFS, MapReduce, Hive, HOD, etc. in a single project is not
scalable. Nigel vetoed this because he thinks it will complicate
QA, but I think (a) it will simplify so many other people's lives
that it is well worth any such cost and (b) the net change in QA
effort will be quite moderate. Yes, there will be more projects to
QA, but they'll be simpler projects.
Modifying the mailing lists is a band aid. It will help those
who're not already doing similar things with filters already, but it
will cause everyone who does have filters to have to re-jigger their
filters. There will be some confusion and time wasted explaining it
to folks.
So I'm fine with this change being made, but it doesn't really
address the glaring problem that we have too much happening under a
single roof.
Doug
Owen O'Malley wrote:
All, core-dev is pretty overwhelming. I'd like to change the jira
notifications so that:
jira created -> core-dev
other jira traffic -> a new list [EMAIL PROTECTED]
Most of us have filters like that anyways, and it would make it a
lot less intimidating for developers getting started. I'm obviously
+1. Thoughts?
-- Owen
