-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Bump Nextcloud to v26.0.7 #2303
Comments
Version 27 is now on .2. It is stable on my MIAB. I’d recommend going directly to that version to prevent the double effort of validating two versions. Version 28 will require us to go to a different PPA again for a higher PHP version. All the required steps for that are in a the repo from before the switch to Ubuntu 22. I’d hold out on that as long as possible since it wasn’t a pleasant change last time I did that. |
Here’s the link to the PR where I added the PPA before: #1140 |
I have been working on a similar PR, but combined it with the upgrade to php 8.1 , see here https://github.com/kiekerjan/mailinabox/tree/nextcloud26 It has been tested for installation, but I did not yet have the time to test some different upgrade paths. |
@kiekerjan Thanks for the inspiration. I like the idea of putting in the PHP version into a variable. May I ask why the PHP v8.1 bump when Nextcloud v26 runs fine on PHP v8.0? I'd do them in separate PRs. |
@yodax Which one PPA? This one |
@yodax also, the bump to Nextcloud v27 will deprecate PHP v8.0, therefore it's not that simple and requires bumping PHP beforehand. That's why I prefer doing all that in smaller steps and PRs. Furthermore, Nextcloud v27 requires nginx changes. |
I
In my mind the upgrade from PHP 8 to 8.1 had to be done during a Nextcloud upgrade. But when I try to explain it, I realize that it actually might not be necessary. I will rebase my branch on your Nextcloud v26 PR and try to come up with something nice. |
Alright @kiekerjan, there won't be any PHP upgrade in my upcoming PR for Nextcloud v26. But I really like the idea of putting the PHP version into a variable. We will need this sooner or later, especially for Nextcloud v27 with different PHP requirements. @kiekerjan would you mind submitting a second PR solely for this, for having the PHP version in one variable? |
Do we need to replace the existing variable in functions.sh?
Just adding my 2 cents 😊 |
I've moved out the suggested PHP works to a separate ticket. This to keep this one pure about Nextcloud alone: |
Here's a pull request upgrading php from 8.0 to 8.1: #2309 |
Thanks, mate @kiekerjan The way I see is that we have to be careful here. For MiaB stability and robustness is the number one priority. So, only introduce changes which are really required. We can still live without PHP v8.1 for now. It's not a priority now I think. That said, I'd like to suggest the following strategy:
If we do these four PRs in isolated commits, all becomes easier to manage any bugs, to investigate problems and to rollback if needed. Thoughts? |
Sure, it's no problem to rebase once #2308 is merged. I'll try to review that one soon then. |
@kiekerjan @yodax @matidau PR is up for Nextcloud v26 - your feedback very welcome |
close? |
Yep, shipped a long time ago :) |
Because the Nextcloud development is rapid (or too rapid?), v26 and 27 are already out and v28 is around the corner
In a summary, v26 doesn't come with many visual changes but many backend refactorings:
To be safe, let's not rush too quickly and bump slowly one version after each in separate PRs for best security and test all well.
PRs for v27 and v28 can come afterwards.
All the breaking changes for v26 are mentioned in:
https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_26.html
Also, within the same PR, bump Nextcloud's user-external, calendar and contact apps to their latest version. user-external is ready, they fixed the bug for v26 recently: nextcloud/user_external#222
When testing, ensure the following:
Feedback welcome before I'll do the PR in the next days :)
The text was updated successfully, but these errors were encountered: