On Thu, May 26, 2016 at 01:22:26AM +0000, Andrew Palumbo wrote: > Currently I don't believe that there Is a reason not to, aside from regular > Jenkins hiccups and some minor addition to the complexity of the example > script
I think there are two questions we should be asking ourselves here: If tomorrow someone comes along and asks us to fix a major bug/security issue, is there someone within our community who has enough insight to be able to do that? Assuming we aren't making any modifications to this part of the code base anyway, what is the advantage for downstream users to keep that code around in newer versions as opposed to using an older release of Mahout? E.g. do they automatically benefit from performance improvements made elsewhere? Isabel
