The captcha code is merged but there is no release candidate yet. Probably only @dessalines knows.
Asklemmy
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
Probably not even him. It'll be done when it's done, including testing. Nobody knows how many serious bugs are there until you test.
This is normally a pretty healthy attitude, but I'm not sure it particularly applies in this case because we know there are serious bugs associated with not releasing:
- We're in the middle of a massive bot registration wave that admins are reporting captchas address.
- The biggest instance, representing 40%+ of the active userbase of the lemmyverse is blocking their upgrade on that feature.
- Jerboa v0.34/0.35 and Lemmy v0.17/0.18 are not cross compatible, leading to many daily confused questions about bug and error messages.
- lemmy.world is also experiencing replication lag that is poorly understood and people think might be addressed by an upgrade, and again this issue affects nearly half the active userbase of the lemmyverse.
- The ONLY feature that needs to be in v0.18.1 is captcha.
Given that we know there are serious ongoing bugs associated delaying the release, and that a release with a very small scope (a single squashed commit) would address those bugs, it's possible to cherry-pick just the captcha commit, test just that change manually, and craft a release whose reasonable bad-case bugs are considerably better than the delay case.
Obviously it's possible that the devs are considering priorities I'm not aware of, but I'm tracking a wide array of support channels and find it hard to imagine that a single-fix release is going to leave us in a worse position than we're in now.
You are not getting a single fix release. There are merged 28 commits since the last release.
18.1-rc1 was tagged half an hour ago, but there is no release built yet for that version. I don't know if Ruud would deploy the first release candidate though.
Cool!
Thanks for pointing that out. I just upgraded!
We've upgraded to 0.18.1-rc.1
- nice UI change, the post view is now wider. No captcha, though. Also the UI is reporting itself to still be 0.18.0
, but that's negligible.