hello jörg. this sounds like a job that should be automated - e.g. using the stale github action [2]. usage example [3].
stefan [2] https://github.com/actions/stale [3] https://github.com/mojohaus/versions-maven-plugin/blob/master/.github/workflows/stale.yml >-----Original Message----- >From: Jörg Hoh <jhoh...@googlemail.com.INVALID> >Sent: Wednesday, August 10, 2022 11:56 AM >To: oak-dev@jackrabbit.apache.org >Subject: 180 open PRs on Github > >Hi, > >On the jackrabbit-oak github repository [1] we currently have 180 open PRs. >The oldest is from 2013 (!) and many of them are of course no longer able >to merge. > >I would like to start some cleanup and close all PRs older than 2020. The >assumption is that these PRs are no longer relevant, because they have been >already addressed in one way or the other. But in any way additional effort >is required to either fix any merge conflicts or check if the PR is still >relevant. > >I suggest this approach: >* add a comment to each of these open PRs older than 2020, and asking if >this PR is still relevant and should be merged. In that case the owner >should revisit the PR and drive it towards merging. >* as a 2nd step I would close all of these PRs which did not receive any >feedback for the update. This would be in around today + 2 months, which >should give everyone enough time to at least put a short comment indicating >the importance of this PR. > >WDYT? > >I would create a ticket for it and also carry out this task. > >(If you are reading this and remember some old PRs of you still being open >but no longer required, feel free to close them already.) > >Jörg > > >[1] https://github.com/apache/jackrabbit-oak > >-- >Cheers, >Jörg Hoh, > >https://cqdump.joerghoh.de >Twitter: @joerghoh
