We actually still haven't recovered from the projects split. We are still fixing HDFS and MR scripts with several jiras open.
If we start this re-split now again before the major release we risk to get into the same mess, and it will create more work for the community. I see Nigel's point that packaging will get easier, and developers will push less buttons when they commit. It will delay the release - this is what worries me. Thanks, --Konstantin On Thu, Jan 13, 2011 at 10:18 PM, Nigel Daley <[email protected]> wrote: > Folks, > > As I look more at the impact of the common/MR/HDFS project split on what > and how we release Hadoop, I feel like the split needs an adjustment. Many > folks I've talked to agree that the project split has caused us a splitting > headache. I think 1 relatively small change could alleviate some of that. > > CURRENT SVN REPO: > > hadoop / [common, mapreduce, hdfs] / trunk > hadoop / [common, mapreduce, hdfs] / branches > > PROPOSAL: > > hadoop / trunk / [common, mapreduce, hdfs] > hadoop / branches / [common, mapreduce, hdfs] > > We're a long way from releasing these 3 projects independently. Given > that, they should be branched and released as a unit. This SVN structure > enforces that and provides a more natural place to keep a top level build > and pkg scripts that operate across all 3 projects. > > Thoughts? > > Cheers, > Nige >
