https://github.com/dessalines/jerboa/issues/891
If you downvote any post in jerboa 0.0.35 you actually upvote it. Seems like anything gets merged? If this goes on like this, there could be a lot of trouble
Edit: Thanks to quick reaction seems like a simple an quick fix. I hope that things will be fine in the future
It’s rough, there are two main developers working on Jerboa, one other person reviewing code, 5 or 6 other people helping squash bugs on the regular. And a few dozen people that even bother to submit PRs every now and then.
The hundreds to thousands of people using the app that aren’t helping to develop it: y’all are the bug testers. It’s good to bring up issues like this one, but it’s the coders that have to go in and fix the issues, hope that they don’t break others in the process (a missing question mark broke all thumbnail displayings at one point mid-development). Lots of issues coming in and not enough hands to both fix them and check that it’s still all working fine. Even the unit tests are coded in by people.
In the next couple days I will try to release something that works well enough for my standards on my fork. But it takes some patience and a little less whining, there’s a reason why we’re in alpha.
I can totally understand the lack of people working on the project. As skeptic I am, I must say that you have total right to not believe me, but I’m an open source developer too with an own project, with literally no time at all since years. But what I’m trying to say: if the devs have no time to review PR-s, and features, please just don’t merge them at all. Please tell me that I’m wrong, but this seems like PR-s getting merged without proper reviews. This is far more worse than not merging any PR-s
I haven’t looked through the Jerboa codebase very closely yet (I downloaded it, but that’s about as far as I have got so far), but it sounds like they either need more code coverage for their unit tests or they need to improve the quality of the unit tests. Good unit tests should catch a lot of bugs introduced by PRs. There is no QA team to do regression testing for each release, and the main developers can’t be expected to run manual testing for every PR. The developer of the PR should be doing that, but clearly they are not.