Re: Organize JIRA Board

The access is working well and thanks for the tips. My first approach, for some cases, will be to contact people to get more information before to take actions on the ticket. Like that, I can see if comments, re-assign or other actions will be necessary. I'll check what I can do in this case of

Re: Spark 2.x/scala 2.11.x release

big +1 If you are planning to branch off the 0.13.0 tag let me know, I have a speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released From: Andrew Palumbo Reply: dev@mahout.apache.org

Spark 2.x/scala 2.11.x release

After some offline discussion regarding people's needs for Spark and 2.x and Scala 2.11.x, I am wondering If we should just consider a release for 2.x and 2.11.x as the default. We could release from the current master, or branch back off of the 0.13.0 tag, and release that with the upgraded

Re: Organize JIRA Board

Andre, I agree with Trevor, this would be great. You've been added to the contributor role. A couple of quick notes: > - Tickets with status "open" and assigned by people (probably the default > when we create tickets) We don't have a default asignee currently; the default when creating a