-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
feat: php 8.2 #40981
feat: php 8.2 #40981
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
07aa0f0
to
429a31f
Compare
|
@DeepDiver1975 CI is working - I will leave you to look at the various things reported by phan, phpstan etc. |
9f6e161
to
30fa310
Compare
e057fb1
to
b9a2f86
Compare
c699ce7
to
b82b5b5
Compare
b82b5b5
to
9a3024f
Compare
…ion during Log::writeExtra
chore: remove email config `mail_smtpauthtype` - this is now auto detected fix: Mailer::send will always thrown an exception in case of errors during delivery
c02ee74
to
aa040d3
Compare
cleaning up - I think this is no longer of anybody's interest |
correction: no longer of interest of anybody from owncloud. This is just infuriating, I guess I have just been a sucker that haven't prioritized the migration away from owncloud a priority. Fwiw, I am also the packager of owncloud-client on nixpkgs. This spells the end of this thing. But I guess that's what owncloud wanted! |
The end of owncloud 10 was marked by the time all forces have been moved to infinite scale. It was quite obvious in all these years. Not really shocking - right? |
That itself was not shocking. The fact that this branch existed and now abandoned signals some change that you folks have all the rights to reserve to yourself. I get that, I guess many people get that. But that's the trust eroded that you won't get back anytime soon. |
Was it really that obvious? At least not for PHP 8.x support (#40241 (comment) from August 2023):
And even if it was "that obvious" for the ownCloud team it wasn't obviously for the community, how should we as users know such stuff like:
Why not just communicate things like this correctly and just disclose the plans from your side? There was not a single real announcement from ownCloud besides that strange announcement about keeping PHP 7.4 support via some third party things in the community forums. How this whole topic was handled from ownCloud side is so awkward / terrible and so frustrating, i can bite into my ass that i have put trust into ownCloud and haven't migrated away earlier. If you can't handle an open source project with the responsibility coming from it like transparent communication then just make your product closed source and don't keep it open in such a pseudo open source way. Farewell ownCloud, time to vanish. |
Description
TODO
Not in scope of this PR
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: