On Wed, Aug 11, 2010 at 10:56 PM, Drew Farris <[email protected]> wrote:
> While I was poking around in hudson to get the mahout-nightly build > working, I noticed that there's some redundancy in the existing Hudson > projects for Mahout and I'd like to get rid of some of the extra > projects, at the very least to make the move to the new Husdon master > easier. > > We currently have: > > mahout-collections-trunk (keep) > Why do we need this separately ? mahout-nightly (builds and deploys nightly snapshots to the apache > maven repo, keep) > +1 Mahout-Patch (remove) > Mahout-Patch-Admin (remove, not sure what these are for, but my gut is > to toss them as they haven't run in 1yr 9mo) > Do you know any way to get these working for patch submissions on JIRA like how Hadoop is doing. Test after commit is not a very good model. Maybe modify MahoutQuality? I couldnt understand how it was being done in the hadoop-qa job, so you are welcome to try. > Mahout-Quality (keep, set up to generate project reports, mark jira issues, > etc) > +100 Mahout-Trunk (remove, just does a clean install, but no deploy, > redundant with mahout-nightly, so toss) > MahoutQM (remove, apparently the old code quality/reporting project, I > think Mahout-Quality covers everything here and more, so toss) +1 on removal > Anyone have any concerns with me removing the redundant projects? > - Drew >
