I can't answer the question directly, but I'll say there's been 3 updates in the last week, and I hear there's another ready to go that hasn't hit the app stores yet.
this post was submitted on 16 Jun 2023
18 points (95.0% liked)
Jerboa
10299 readers
3 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
- Open source, AGPL License.
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
- bitcoin:
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK - ethereum:
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01 - monero:
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV - cardano:
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Contact
founded 2 years ago
MODERATORS
Crazy how fast the devs started churning out updates since the whole Reddit fiasco started approaching. I don't know how they managed this during this turbulent time, while also running the lemmy.ml instance. Truly rising to the occasion.
It helps that a bunch of the devs that were on reddit came here. In the two and a bit weeks I've been lurking then made an account the jerboa github has doubled in contributers at the least.
He'll tickle your feet when he's ready to release
Usually tickling his feet makes him release.
Just leave us your address below and we'll send over a personal feet tickling service. Six hour guarantee!
I think releases are just whenever they're ready
AKA the best release schedule
Software development takes time and has many unanticipated challenges that makes time estimation difficult. When developers do provide estimates users, managers etc then get stroppy when they slip by.
Therefore the best strategy is just to ignore requests for time schedules because it's a no win situation.
Software development takes time and has many unanticipated challenges that makes time estimation difficult. When developers do provide estimates users, managers etc then get stroppy when they slip by.
Therefore the best strategy is just to ignore requests for time schedules because it's a no win situation.
I think you might be confusing estimates and fixed-cadence releases. It's really simple to provide a promise of fixed-cadence releases - just take whatever changes are merged (if any) and release them on the cadence.
Promising to release a specific feature within a specified timeframe is a different beast entirely.