-
Notifications
You must be signed in to change notification settings - Fork 13
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
Nextcloudd 20 #32
Comments
Same question here! Did anybody tried that? |
This app uses multiple features that have been deprecated for Nextcloud 20 (see nextcloud/server#20953). Specifically |
This is currently blocking my update to NC20, an update would be highly appreciated 😊 |
@jacotec Here's something you might benefit from reading: https://journal.neilgaiman.com/2009/05/entitlement-issues.html To paraphrase Neil Gaiman: @daita is not your bitch. This is open source software. As far as I know, you have not paid for it, and @daita is not on your payroll, nor are they your property. Therefore, they don't owe you anything. I appreciate that this is inconvenient for you, and understand that you're annoyed. This is blocking me upgrading as well. Taking it out on the author does not help. You're more than welcome to:
As an open-source author myself, I can tell you that: pestering, berating, or venting at an author, who donated their time and hard work for nothing in return, tends to get work de-prioritized, or even dropped. Open-source software thrives when there is a supporting community. Please be part of one. </rant> |
@jacotec I accept that you may not have intended offense, but it is the person on the receiving end that determines if they were offended, not the giver of offense. The onus is on you to ensure your words match your intention. I, for one, was offended by your tone to the extent that I felt a response was warranted (I accept that this is a hot-button topic for me, but if you actually read the blog post I linked, you'll understand my choice of words). If you did not intend offense, I suggest you reconsider your wording. You could have simply asked for an update, no need to state the amount of time that has passed, express your annoyance and displeasure, or put blame on the author for your inability to update. |
@plinss I've edited my post, not because of your aggressive comment but to prevent that @daita misunderstands it, which is not my intention. @plinss If you think that someone's comment could be misunderstood or appears unfriendly to you, a friendly hint is always welcome and has more effect than pulling the Bazooka and shoot right away! I don't think Daita or anyone else wants you to be his personal Rambo. |
... just a polite question if this project is still active? |
yes, a release for nc20 should be available |
I and a couple of other people have found that on updating a 19.0.6 installation to 20.0.3, indexing new documents fails when fulltextsearch_tesseract is enabled. (see nextcloud/files_fulltextsearch#100) Apologies if this was already known - i just didn't know it didn't work in nc20 so I was confused when it broke. Should it maybe be marked as incompatible with nc20 so users can avoid updating if they want? |
Support for Nextcloud Version 20 was added in the following commit and tag: Closing this, the original issue is resolved, reported problems are likely to be superseded and should be in their own issue anyway. |
Hello, is there an update planned for nextcloud 20?
The text was updated successfully, but these errors were encountered: