You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Gerardo Curiel <ge...@gerar.do> on 2018/08/22 08:42:43 UTC

Jira cleanup and triage

Hi folks,

Is there a recommended way for contributors to help close/triage Jira
issues?

I've been looking at issues to work on next, and I've found a few
categories of issues:

- Issues in need of triage: these might need to be checked against the
latest version and then closed if they can't be reproduced
- Duplicated issues
- Issues that are still open issues with merged PRs (one example:
https://issues.apache.org/jira/browse/AIRFLOW-2856)

How can we help to point out these out to committers? Cleaning up Jira
should help newcomers to easily visualise the work being done and pick what
to work on.

Also, has something like https://github.com/probot/stale (or whatever the
equivalent in Jira is) being considered for closing issues and PRs
automatically?

Cheers,

-- 
Gerardo Curiel // https://gerar.do

Re: Jira cleanup and triage

Posted by Naik Kaxil <k....@reply.com>.
Thanks @Gerado, Appreciate that. I have closed/resolved the JIRAs.

On 24/08/2018, 05:07, "Gerardo Curiel" <ge...@gerar.do> wrote:

    Hi Kaxil,
    
    On Wed, Aug 22, 2018 at 6:53 PM Naik Kaxil <k....@reply.com> wrote:
    
    > Wherever you see a an open issue associated with merged PR, please mention
    > the contributor who merged it on the Jira issue or the associated PR.
    >
    > I am happy to review jiras, so please tag/mention me on the jira issues
    > you think needs review, are duplicates etc.
    >
    
    Nice! thanks for that. I'll tag you in a few of these open issues soon.
    
    Cheers,
    
    -- 
    Gerardo Curiel // https://gerar.do
    
    
    



Kaxil Naik 

Data Reply
2nd Floor, Nova South
160 Victoria Street, Westminster
London SW1E 5LB - UK 
phone: +44 (0)20 7730 6000
k.naik@reply.com
www.reply.com

Re: Jira cleanup and triage

Posted by Gerardo Curiel <ge...@gerar.do>.
Hi Kaxil,

On Wed, Aug 22, 2018 at 6:53 PM Naik Kaxil <k....@reply.com> wrote:

> Wherever you see a an open issue associated with merged PR, please mention
> the contributor who merged it on the Jira issue or the associated PR.
>
> I am happy to review jiras, so please tag/mention me on the jira issues
> you think needs review, are duplicates etc.
>

Nice! thanks for that. I'll tag you in a few of these open issues soon.

Cheers,

-- 
Gerardo Curiel // https://gerar.do

Re: Jira cleanup and triage

Posted by Naik Kaxil <k....@reply.com>.
Hi Gerado, we previously used a tool for merging PRs and closing Jira but recently we have moved to Gitbox where we now have permissions to merge a PR from the Github UI itself. 

Wherever you see a an open issue associated with merged PR, please mention the contributor who merged it on the Jira issue or the associated PR.

I am happy to review jiras, so please tag/mention me on the jira issues you think needs review, are duplicates etc.

Regards,
Kaxil

On 22/08/2018, 09:43, "Gerardo Curiel" <ge...@gerar.do> wrote:

    Hi folks,
    
    Is there a recommended way for contributors to help close/triage Jira
    issues?
    
    I've been looking at issues to work on next, and I've found a few
    categories of issues:
    
    - Issues in need of triage: these might need to be checked against the
    latest version and then closed if they can't be reproduced
    - Duplicated issues
    - Issues that are still open issues with merged PRs (one example:
    https://issues.apache.org/jira/browse/AIRFLOW-2856)
    
    How can we help to point out these out to committers? Cleaning up Jira
    should help newcomers to easily visualise the work being done and pick what
    to work on.
    
    Also, has something like https://github.com/probot/stale (or whatever the
    equivalent in Jira is) being considered for closing issues and PRs
    automatically?
    
    Cheers,
    
    -- 
    Gerardo Curiel // https://gerar.do
    
    
    



Kaxil Naik 

Data Reply
2nd Floor, Nova South
160 Victoria Street, Westminster
London SW1E 5LB - UK 
phone: +44 (0)20 7730 6000
k.naik@reply.com
www.reply.com

Re: Jira cleanup and triage

Posted by Gerardo Curiel <ge...@gerar.do>.
On Wed, Aug 22, 2018 at 6:51 PM Driesprong, Fokko <fo...@driesprong.frl>
wrote:

> Recently we've moved the Apache Airflow repo to the Gitbox repo (
> https://gitbox.apache.org/). Before with the Apache repo, the Github repo
> was just a mirror of the Apache one. Now we do everything on Github itself.
> We still need to hook up the hooks to automagically close a Jira issue when
> the PR is being closed. This would work very well combined with the stale
> robot.
>

Sounds good!

Ps. If you're looking for a new ticket, the CI still needs to cache the
> Docker images instead of pulling them every time ;-)
>

Heh, I'll have a look :-)

Cheers,

-- 
Gerardo Curiel // https://gerar.do

Re: Jira cleanup and triage

Posted by "Driesprong, Fokko" <fo...@driesprong.frl>.
Hi Gerardo,

Thanks for bringing this up. This is actually a good point.

Recently we've moved the Apache Airflow repo to the Gitbox repo (
https://gitbox.apache.org/). Before with the Apache repo, the Github repo
was just a mirror of the Apache one. Now we do everything on Github itself.
We still need to hook up the hooks to automagically close a Jira issue when
the PR is being closed. This would work very well combined with the stale
robot.

For the Jira tickets itself, sometimes one of the committers goes through
the list of open tickets. I did that two month ago or so. We don't have an
explicit process in place to be honest.

I think in terms of contributing, checking stale PR's would be awesome of
course.

Cheers, Fokko

Ps. If you're looking for a new ticket, the CI still needs to cache the
Docker images instead of pulling them every time ;-)





2018-08-22 10:42 GMT+02:00 Gerardo Curiel <ge...@gerar.do>:

> Hi folks,
>
> Is there a recommended way for contributors to help close/triage Jira
> issues?
>
> I've been looking at issues to work on next, and I've found a few
> categories of issues:
>
> - Issues in need of triage: these might need to be checked against the
> latest version and then closed if they can't be reproduced
> - Duplicated issues
> - Issues that are still open issues with merged PRs (one example:
> https://issues.apache.org/jira/browse/AIRFLOW-2856)
>
> How can we help to point out these out to committers? Cleaning up Jira
> should help newcomers to easily visualise the work being done and pick what
> to work on.
>
> Also, has something like https://github.com/probot/stale (or whatever the
> equivalent in Jira is) being considered for closing issues and PRs
> automatically?
>
> Cheers,
>
> --
> Gerardo Curiel // https://gerar.do
>