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 <gera...@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 >
