Thanks Lynn! As I first step I’d like to focus on issues labeled as ‘CI’. There are 220 open issues and 148 [1] of those have been open for > 1 year. If I look at the metrics jobs [2, 3, 4] I see a clear mismatch between failures that are currently relevant and our JIRA backlog. That is, a bunch of tests that used to fail don’t anymore. Perhaps that’s because of the transition away from Jenkins or something else, but it makes it hard to figure out what is important. GEODE-552 [5] is a good example—is this still a problem and if so is it worth doing compared to more recent issues?
So I’d like to make a radical proposal: let’s close out all 148 of those stale CI issues. If a test failure recurs, we can always reopen the ticket. Why I think this is important: I’ve noticed a few reports from users that did not get timely attention and caused frustration. I think reducing the sheer volume of issues will help us focus on the most important issues. Let me know what you think. Thanks, Anthony [1]https://issues.apache.org/jira/issues/?filter=12343689&jql=project%20%3D%20GEODE%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20%3D%20Unresolved%20AND%20(labels%20in%20(CI%2C%20Ci%2C%20ci%2C%20Flaky%2C%20flaky)%20OR%20summary%20~%20ci)%20and%20created%20%3C%3D%20%20-52w%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC%2C%20updated%20DESC [2] https://concourse.apachegeode-ci.info/teams/main/pipelines/develop-metrics/jobs/GeodeDistributedTestMetrics/builds/66 [3] https://concourse.apachegeode-ci.info/teams/main/pipelines/develop-metrics/jobs/GeodeIntegrationTestMetrics/builds/66 [4] https://concourse.apachegeode-ci.info/teams/main/pipelines/develop-metrics/jobs/GeodeFlakyTestMetrics/builds/66 [5] https://issues.apache.org/jira/browse/GEODE-552 > On Apr 20, 2018, at 3:19 PM, Lynn Hughes-Godfrey <lhughesgodf...@pivotal.io> > wrote: > > I can help with that. > > > On Fri, Apr 20, 2018 at 1:46 PM, Anthony Baker <aba...@pivotal.io> wrote: > >> I surfed through our JIRA backlog and cleaned up a bunch of old >> issues—primarily issues that we missed resolving when the fix was made. In >> some cases I asked for help determining if the issue should be closed. If >> you got one of these requests please try and follow up in the next week or >> so and close if needed. >> >> There are a number of issues remaining that probably deserve a deeper >> review. Some of these include: >> >> - Bugs that have insufficient detail and can’t be reproduced >> - Tasks that may no longer be relevant >> - Ideas that are good but we may never get around to doing them >> - CI failures that no longer occur >> >> Ideally I’d like to close out issues where appropriate to make the backlog >> more manageable and approachable. Any volunteers to help with this effort? >> >> Anthony >> >>
