I know this comes up with every release of NC but the way I understand it still seems to be wrong.
I thought that the update is rolled out in portions and not before the release of a first minor version, but we are now on NC22.1.1. And the first version was released more than two month ago.
Has the updater (web or command line) suggested an update to NC22 to anyone of you when on stable channel? Iâm on NC21.0.4.
Or is NC22 still considered beta until the release of a first NC23 version?
There are people who certainly do consider that, regardless of what status Nextcloud assigns to it. I think Nextcloud releases a little bit too often and often too early⌠In many cases it could be better to stay on an older version longer, except you absolutly need a new feature that was announced for the new version. What you always should check with every major version upgrade before you actually hit the Upgrade button, is whether all the apps you are using are compatible with the new version.
Anyways⌠This is a topic in itself
If you want to update immediately, you can change the channel to beta. When version 21.1.1 is presented to you, you will actualy get the current stable release. After the upgrade just switch back to the stable channel.
Hi,
I got 22.1.1 and I am on release channel. I do not know when I got it but it was several days ago. I use the web updater and NC is running in docker.
Docker still shows the current stable release to be 21.0.4, I tried to upgrade to NC 22 last weekend, and immediately regretted the decision, the upgrade page showed that about 50% of what I was running in my current environment was not currently compatible with NC 22, Maria DB still has to stay downgraded as well from current version as NC doesnât support the âCOMPRESSâ feature. I was bummed because I was looking forward to some of the new announced features of NC 22. I believe that NC 22 is still very much Beta and will let the developers continue to built it into a stable platform.
I second that. I learned the hard way as you did. I decided to update to 22 just to find that the featured app âgroupfoldersâ was still in beta for 22. On top of that, discovered that developers of that app have a lot of issues to solve even on the 21. Donât get me wrong, I am not bashing the app. On the contrary, I congratulate them, as they are very active to solve the appâs problems. It is only natural that each [featured] app has a specific battle, so this perhaps come into play when we receive the update.
While I was at it, I tried to update to PHP8, but I had a lot of issues and found little information yet on how to properly do the transition [I am sure someone will say it is dead easy below], despite the fact that 7.4 is hitting its end of life next year.
In summary, I will just relax and enjoy the outdated but supported versions to give some overhead as the releases of each piece are not synced.
I found this (by searching the forum, sorry @JimmyKater ) :
'21.0.4' => [
'30' => [
'latest' => '22.1.1',
So 30% of requests get an update from 21.0.4 to 22.1.1.
According to your comments I will update my home server (quite simple config) as soon as it will be suggested and on the work server (groupfolders app, etc.) I will wait a little bit longer (Despite we would like to have the feature to book ressources).
This is my only real complaint about all the various server applications using âpluginâ technology vs. writing features directly into their software. I appreciate the flexibility of adding only the features you need as everyoneâs installations are unique. But âdown the roadâ upgrades have become IT nightmares along with the issues of being able to continue offering your users capabilities when someone decides to drop a plug-in project and it is no longer available. It would be nice if there was some type of framework, modularity or version control that would allow you to âfreezeâ a portion of the master code that said âok, these plugins or features meet the version 20 master frameworkâ and you could freeze that portion of the code and that plugin would continue to work in perpetuity regardless of what changes were made to the master framework down the road. I know, I knowâŚ
I think Nextcloud releases a little bit too often and often too early⌠In many cases it could be better to stay on an older version longer, except you absolutly need a new feature that was announced for the new version. What you always should check with every major version upgrade before you actually hit the Upgrade button, is whether all the apps you are using are compatible with the new version.
) :