-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release timeline for v1.8.11 #1051
Comments
See the community fork Orgzly Revived with many merged fixes at https://github.com/orgzly-revived/orgzly-android-revived. Join us and spread the word! There's in progress work on getting the forked package onto F-Droid and Obtainium. |
Glad to see the community has revived development on this great app! Unfortunately, I use a corp-managed device and can only install apps from the Play Store. I'll watch the tracking issue for orgzly-revived. I'd love to see the clock-in/clock-out feature land there! I'm glad orgzly-revived is there for others through F-Droid et al. |
The 1.8.11 (and 1.8.12) have been released! |
for the record, as of 2023-11-24 this comment is talking about orgzly-revived. orgzly is still at 1.8.10. (just clarifying, since I just checked the Playstore and was confused ;-) |
True. And, as things currently stand (one year since the last commit or any signs of life in Orgzly) it looks like it's going to remain that way. Which is exactly the reason we went ahead with the Orgzly Revived project. |
This isn't so much a feature request as a request: Please release v1.8.11.
There's one issue remaining in the milestone (#1000). Can we move it to v1.8.12 and release v1.8.11? It's been ~1 year since the last merge and I think it'd be best to release the work that's already been done.
The text was updated successfully, but these errors were encountered: