Open JJ opened 5 years ago
@vrurg I gave some links via IRC
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 ...
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
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?
So, some possible ideas to solve that:
Any new idea? What would be the best way to deal with this?