Because there is not one right answer. If you only use the core apps and the hub package, you can update. Beyond that, however, every Nextcloud instance is different and the extensions are sometimes developed by completely different teams and also external volunteers, then there are 3rd party apps etc ppp. In order to provide precise recommendations on the blog you would have to hire someone that has an overview of all the projects related to Nextcloud, who then constantly updates the blog.
If you self-host a relatively complex server software like Nextcloud, you are no longer just a user but also a sysadimin, and for sysadmins it is common sense to at least inform themselves first, but better to have a separate test instance, and only touch the production instance when everything is tested.
If you can’t or don’t want to do that (not you personally ) go use a hosted solution or hire an MSP and let them do it for you. Or as a home user use an appliance like AIO or NCP and stick to the recommendations of the maintainers of these appliances rather than marketing blogs.
Well this chapter in the docs was greatly expanded early this past year in part for this very reason, but I have no idea how many admins actually read it.
support defining local update policies with greater granularity
interact symbiotically with the various methods of installing Nextcloud (i.e. Archive, Containers/Images, Snap, third-party, etc).
The point is to empower and encourage admins to define their own local update policies that match their priorities and goals (while having some sensible defaults) and to arm them with the info needed (in a single place) to increase the odds of a successful upgrade.
Thanks for putting in the work, that would be very helpful!
I don’t think I read it in detail before, because it contains nothing unexpected. But I saw a link to Maintenance-and-Release-Schedule, which is very helpful as an overview. Unfortunately the wiki does not give the option to subscribe to a page so I’d get notified on updates, but it is certainly a very useful overview that I did not know about.