There are some apps missing. So for those that rely on self-installed apps not bundled with NC itself, make sure that they do work fine on NC19 prior to scheduling the update. For me (sorted by priority), these apps do work fine on NC19: two factor…, nextbackup, group folder, polls, bookmarks, preview generator, rainloop. These work fine but they are “not compatible”: Impersonate (marked “official”, yet “not compatible”?!, two factor e-mail. These don’t work yet or are not marked compatible yet: group quota, onlyoffice (marked official but incompatible!?) community document server(!), external user authentication, checksums, occ web, ransomware… . Of course there are more apps, I only listed those that seem relevant to a wider audience.
I think of all these, the team should ensure that these are available when NC 19 gets released: impersonate, community document server, onlyoffice, external user authentication.
I installed 19. Unfortunately the system did not create the right database entries for contacts. I was not able to add any. The error message I got was something with import of contacts disabled because there was no address book. I manually had to add the system and the admin user to the oc_addressbooks table (compared it to my production environment). From there it seemed to work fine.
I always have a /var/www/testcloud installation on my machine, where I install the beta version. Of course you also need a separate data directory, and a dedicated vhost like testcloud.mydomain.com to let it run separately.
It’s a pity that there is no more information about new features. This is kind of essential for good testing. Well we can look for ourselves, checkout github issues, but that takes more time we could spend in more specific testing.
Please don’t forget about the apps. Many are community driven and need support to get updated and tested.
So if it’s a bugfix release, why is the major version number being incremented?
Just to break compatibility with 3rd party apps for no good reason?
Someone at Nextcloud needs to learn semantic versioning (https://semver.org). Users would be much better served by an 18.1 release than a 19.0 release with no significant user visible differences. Even from a purely marketing perspective, it sends a clearer signal.
Please stop incrementing major version numbers unless there’s a significant reason to do so, like a major new feature, or a change that breaks compatibility for apps.
We don’t know that. New features could be in some apps, or even completely new apps that are not public yet. You can just guess from what you see in the new version and what is on github. And even then, there could be some hidden things, that break compatibility that would justify a new version number.
I know we don’t know that, I was responding to @Paradox551’s statement.
But even if all the new features are just in apps, that doesn’t justify a major version change.
And frankly Nextcloud’s lack of communication about features and potential breaking changes in new releases is a problem in and of itself. If app authors really need to update their apps for compatibility, wouldn’t users be better served if the authors had the information they needed to update their apps before the Nextcloud release? The silence helps no one.
Every time there’s a major version change, there’s a whole raft of apps that stop working, even though the majority only need their compatibility information updated. This just creates unnecessary havoc.
A sensible versioning system, that actually advertises compatibility for apps would allow most apps to just keep working. e.g. SemVer
Don’t get me wrong, I appreciate the rapid addition of features and release cadence, it just needs to be done in a way that isn’t so disruptive to users and 3rd party developers.
Activities for shared file downloads, visible to all admins
Full text search
Full text search - Elasticsearch Platform
That’s a significant list. An upgrade now would have a major impact for me, so I will not be helping test V19. Now, if there’s really nothing other than bugfixes in the core server, I expect all of these apps to work just fine. However, since those apps don’t claim to work with V19, they’re all going to get disabled in an update, or prevent me from wanting to update in the first place. How is that helping anyone?
If the release were marked as V18.1, (and Nextcloud actually followed the semantic versioning contract) then I’d expect most (or all) of those apps to claim to still be compatible without the app author having to issue a new release just to bump the version number.
Yes, I know it hasn’t released yet, but this situation happens every time there’s a major version change and there are always a significant number of apps that haven’t updated their compatibility info when the release actually happens, sometimes taking months to update because the developers have other jobs. Often many of them require no changes other than the compatibility info. This puts a completely unnecessary burden on app developers and users alike. I’m asking Nextcloud to re-think their versioning system.