Skip to content

Conversation

@binford6000
Copy link
Contributor

@binford6000 binford6000 commented Dec 2, 2025

Some customers already migrated from 10.15.3 and needed to edit the version.php file before the migration. 10.16 was recently published and it seems migration from there also works fine.

nextcloud/documentation#13910

  • Resolves: #

Summary

TODO

  • ...

Checklist

@binford6000 binford6000 requested a review from a team as a code owner December 2, 2025 09:01
@binford6000 binford6000 requested review from Altahrim, ArtificialOwl, icewind1991 and leftybournes and removed request for a team December 2, 2025 09:01
Copy link
Contributor

@szaimen szaimen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but did not test

],
'owncloud' => [
'10.13' => true,
'10.14' => true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought 10.14 does not exist?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does - but never saw it in the wild...

@szaimen
Copy link
Contributor

szaimen commented Dec 2, 2025

@binford6000 please check the failing CI. Seems to be related

@AndyScherzinger AndyScherzinger added this to the Nextcloud 33 milestone Dec 2, 2025
binford6000 and others added 2 commits December 2, 2025 14:40
Some customers already migrated from 10.15.3 and needed to edit the version.php file before the migration. 10.16 was recently published and it seems migration from there also works fine.

Signed-off-by: Sebastian Möbus <[email protected]>
@AndyScherzinger AndyScherzinger force-pushed the binford6000-patch-upgrading-from-owncloud->-v10.13 branch from 3b5412a to f562053 Compare December 2, 2025 13:40
@AndyScherzinger
Copy link
Member

The branch name is invalid, at least on windows... so I can't fix the commit messages

@szaimen
Copy link
Contributor

szaimen commented Dec 2, 2025

The branch name is invalid, at least on windows... so I can't fix the commit messages

Same for me unfortunately

@binford6000 binford6000 merged commit bae24eb into master Dec 3, 2025
178 of 191 checks passed
@welcome
Copy link

welcome bot commented Dec 3, 2025

Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22

@binford6000 binford6000 deleted the binford6000-patch-upgrading-from-owncloud->-v10.13 branch December 3, 2025 05:42
@AndyScherzinger
Copy link
Member

I think this needs some backporting to 25, no?

@AndyScherzinger
Copy link
Member

/backport to stable27

@AndyScherzinger
Copy link
Member

/backport to stable26

@AndyScherzinger
Copy link
Member

/backport to stable25

@AndyScherzinger
Copy link
Member

backports matching #40977

@AndyScherzinger
Copy link
Member

Docs PR nextcloud/documentation#13910

@szaimen
Copy link
Contributor

szaimen commented Dec 5, 2025

@AndyScherzinger I am not sure about the backports. Peobably backporting to nc32 for now is enough? Wdyt @binford6000 ?

@binford6000
Copy link
Contributor Author

@AndyScherzinger I am not sure about the backports. Peobably backporting to nc32 for now is enough? Wdyt @binford6000 ?

Usually our customers want to migrate to latest or latest-1. So Backporting to 31 would be sufficient in my opinion.

@AndyScherzinger
Copy link
Member

Usually our customers want to migrate to latest or latest-1. So Backporting to 31 would be sufficient in my opinion.

But see the docs, wouldn't you update to latest v10 cO, than v25 Nc (due to the PHP requirements) and than upgrade Nc versions from there?

@binford6000
Copy link
Contributor Author

Usually our customers want to migrate to latest or latest-1. So Backporting to 31 would be sufficient in my opinion.

But see the docs, wouldn't you update to latest v10 cO, than v25 Nc (due to the PHP requirements) and than upgrade Nc versions from there?

Sure, but looking at my last big migrations people turn on maintenance mode, stop webserver/php, bump php to 8.3 and then start occ upgrade with NC31/32 directly which definitely is proven to work (ETH Zurich, upcoming SWITCHdrive and others). One could say that our documentation would need to be updated as well...

@AndyScherzinger
Copy link
Member

/backport to stable32

@AndyScherzinger
Copy link
Member

/backport to stable31

@AndyScherzinger
Copy link
Member

/backport to stable25

@szaimen
Copy link
Contributor

szaimen commented Dec 9, 2025

/backport to stable25

I guess 26-30 is needed in that case as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants