Re: Organize JIRA Board

[André Santi Oliveira]

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 the overlap. Maybe it'll be
necessary to contact other groups but I'm ready to help on that as well.

In case you don't agree with the actions I'm taking, please feel free to
give feedback as I'm totally open to it.


Cheers,
André

On Wed, Feb 28, 2018 at 2:11 PM, Andrew Palumbo  wrote:

> 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
> ticket is "unassigned"
>
> >   - Sprint from 2016 still open with no content inside
> >   - Sprint name not matching with initial/end date
>
> We've been unable to delete some of the sprint boards, since they some
> happen to overlap other projects, due to the way that ASF Jira is
> configured.  This is something that we've had to co-ordinate with INFRA for
> ,so you may need to discuss some issues with them.
>
>
> This would be a great help for the project.
>
>
>
> Thanks very much.
>
>
> --andy
>
>
> 
> From: Trevor Grant 
> Sent: Friday, February 23, 2018 3:46:13 PM
> To: Mahout Dev List
> Subject: Re: Organize JIRA Board
>
> Hi Andre,
>
> That sounds great.
>
> We need to talk to INFRA about how to get you permissions.
>
> Will let you know shortly,
>
> tg
>
>
> On Thu, Feb 22, 2018 at 11:59 PM, André Santi Oliveira <
> asobra...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I'm interested in collaborating with Mahout project and I've followed the
> > process to build Mahout from the source and so far it looks like
> everything
> > is working well.
> >
> > Then I jumped into your JIRA board and it looks like you need some help
> to
> > organize that part. Simple things I saw which could be organized like:
> >
> >   - Tickets with pull requests available but not linked to the ticket
> >   - Tickets with status "open" and assigned by people (probably the
> default
> > when we create tickets)
> >   - Sprint from 2016 still open with no content inside
> >   - Sprint name not matching with initial/end date
> >   - and so on...
> >
> > I really like this part of organizing things and I believe I can start
> help
> > on that. But to help you with this I need a specific access to JIRA (more
> > than a simple user that can just create tickets and put comments).
> >
> > Let me know what you think and if you need more information to trust me
> on
> > that.
> >
> >
> > Cheers,
> > André
> > https://github.com/ASOBrasil
> >
>

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

[Pat Ferrel]

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  
Date: February 28, 2018 at 11:16:12 AM
To: dev@mahout.apache.org  
Subject:  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
defaults, and branch our current multi-artifact build off as a feature. Any
thoughts on this?


--andy

Spark 2.x/scala 2.11.x release

[Andrew Palumbo]

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 defaults, and 
branch our current multi-artifact build off as a feature.  Any thoughts on this?


--andy

Re: Organize JIRA Board

[Andrew Palumbo]

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 ticket 
is "unassigned"

>   - Sprint from 2016 still open with no content inside
>   - Sprint name not matching with initial/end date

We've been unable to delete some of the sprint boards, since they some happen 
to overlap other projects, due to the way that ASF Jira is configured.  This is 
something that we've had to co-ordinate with INFRA for ,so you may need to 
discuss some issues with them.


This would be a great help for the project.



Thanks very much.


--andy



From: Trevor Grant 
Sent: Friday, February 23, 2018 3:46:13 PM
To: Mahout Dev List
Subject: Re: Organize JIRA Board

Hi Andre,

That sounds great.

We need to talk to INFRA about how to get you permissions.

Will let you know shortly,

tg


On Thu, Feb 22, 2018 at 11:59 PM, André Santi Oliveira 
wrote:

> Hi,
>
> I'm interested in collaborating with Mahout project and I've followed the
> process to build Mahout from the source and so far it looks like everything
> is working well.
>
> Then I jumped into your JIRA board and it looks like you need some help to
> organize that part. Simple things I saw which could be organized like:
>
>   - Tickets with pull requests available but not linked to the ticket
>   - Tickets with status "open" and assigned by people (probably the default
> when we create tickets)
>   - Sprint from 2016 still open with no content inside
>   - Sprint name not matching with initial/end date
>   - and so on...
>
> I really like this part of organizing things and I believe I can start help
> on that. But to help you with this I need a specific access to JIRA (more
> than a simple user that can just create tickets and put comments).
>
> Let me know what you think and if you need more information to trust me on
> that.
>
>
> Cheers,
> André
> https://github.com/ASOBrasil
>