There's a huge PR/issue deficit in the Rakudo repo

JJ commented 5 years ago

Only one issue is closed for every 6 open (roughly), and one PR for every two. There are too many PRs, and that will discourage people from sending new PRs. Someone with a stale PR from two years ago will probably never contribute again to the community. So, can you think about some way to deal with this? Clear the backlog of PRs and try to get a bit more up to date with issues?

Branches are also a problem. There are more than two hundred. That's probably better left to another issue here.

So, some possible ideas to solve that:

Devote part of the time every release to address and clear old PRs. Maybe devote exclusively a release cycle (maybe the one in the summer?) to review and accept/comment/close old PRs.
Deal with new issues ASAP: at least label them, vet them (for adequacy, relatedness) and close them if they are not going to be addressed
Devote one squashathon to them?

Any new idea? What would be the best way to deal with this?

melezhik commented 3 years ago

@vrurg I gave some links via IRC

melezhik commented 3 years ago

I've converted sparrow tasks for existing rakudo bugs into tomty tests and run them through my own CI server - http://161.35.142.50/report/rakudo-old-bugs/47 , this could be easily adjusted to run against any new rakudo commit or whatever period we want to or on demand ...

melezhik commented 1 year ago

Btw , if this is still relevant , R3 tests get run from time to time by me for the fresh Rakudo commits to validate that closed bugs pass their tests and open bugs fail their tests, I could elaborate more on how all this works in details …

The latest R3 report - https://ci.sparrowhub.io/report/3082

Raku / problem-solving

There's a huge PR/issue deficit in the Rakudo repo #5