The StaleBot is now active, running once a day at midnight. I started in a conservative way, only labeling 10 PRs a day, and setting the threshold at 60 days. This gives us some time to evaluate without labeling the entire backlog. Will be interesting to see whether the Bot results in some fogotten PRs being completed.
Jan > 8. jan. 2024 kl. 23:10 skrev Jan Høydahl <jan....@cominvent.com>: > > Hi, > > Got some initial (positive) feedback on the auto-categorization PR and plan > to merge on Thursday, giving you some more time to review. I feel I have not > 100% nailed perfect labels. Obviously we can't auto label things like > feature/bug, or versions, so this is only a "category". Ideally there would > be a a 1:1 between these "category" labels and the "Components" defined in > JIRA. But here are 96 different "Components" there, most of them are > old/irrelevant and not always very good IMO. So I'd rather attempt to align > JIRA components with whatever we come up with here... > > Lucene has just put their StaleBot to work, and I created > https://github.com/apache/solr/pull/2184 to do the same for Solr. Have a look. > > Jan > >> 6. jan. 2024 kl. 01:21 skrev Jan Høydahl <jan....@cominvent.com>: >> >> Hi, >> >> We tend to not use the GitHub's PR labels we have defined. >> So I whipped up https://github.com/apache/solr/pull/2180 which is configured >> to auto-label PRs based on what files are changed. Feedback welcome. >> >> Also, I hope we can implement StaleBot for labeling PRs as stale. Lucene is >> going to test it, see https://github.com/apache/lucene/pull/12813. If that >> goes well, let's copy their config :) >> >> - Jan >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
