this post was submitted on 27 Jun 2023
9 points (62.2% liked)

Jerboa

10300 readers
1 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
dessalines@lemmy.ml
9
Jerboa is not trustable with these bugs, seems like any PR gets merged (sh.itjust.works)
submitted 1 year ago by catlover@sh.itjust.works to c/jerboa@lemmy.ml
17 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[โ€“] catlover@sh.itjust.works 2 points 1 year ago (1 children)

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

[โ€“] dandroid@dandroid.app 1 points 1 year ago

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.