Thatâs not enough. Itâs not possible to see which version is in which release channel from that. This is now the 20th post and no one could tell me which version is in which release channel so far. A bit disappointing.
Go to your admin page and switch the setting between the release channels and it will show you which version is available for update.
It always shows 11.0.3
My mistake, it only shows the version if it is more recent than what you have installed.
+1 @glotzbachâs GH issue then. That info clearly isnât readily available so youâll have to wait for a team member to see your question.
1 Like
and from that you can surmise weâre not ready with 12.0.1 yet - good chance itâll skip to next week, sorry!
We could add some info to the updater about us doing staged roll-outs and deciding to make a new version available when we feel comfortable with it etc etc. yeah.
Ok, thinking about it, that is probably a good idea. so:
Input welcome 
The question was less about staged roll-outs. The question was more like where to see what is production. Even with a staged-rollout there should be some time where you say âokay this is production, we can push it to all users having selected the production release channelâ, but this information is nowhere to find and new users currently always get the most recent release for download although it might not even be stable (e.g. why is currently the default download v12 although it seems not to be stable while it is quite hard to find a link to an older version from the download page?).
This is actually not possible. Or from what should I know that 11 with open issues is stable but 12 with open issues is not?
12 is stable - we released it after extensive testing. We couldnât find any more big issues. After release, we discovered some (broken) clients had trouble with the CalDAV/CardDAV support so we delayed rolling out updates to users on the Stable channel.
There is absolutely no way to ensure something like that NEVER happens, this is software - there will be bugs. If not in our software, then in other peopleâs software, like in this case.
So if you want the latest stable: Download and install Nextcloud
The fact that we have not rolled it out to users is simply because we want to avoid this problem for them. We did not consider the problem important enough to remove our 12.0.0 release, though, new users will set it up, MIGHT find out thereâs this problem - which will be fixed in 12.0.1. Or people update manually and find out - also not a huge deal.
Is this arbitrary? Yeah, it is a bit. Generally we try to push out the .0.1 release within 2 weeks, so it isnât a big deal. We were slower this time due to a rather sudden big influx of customer work so we havenât merged everything weâd like to have in the bugfix release⌠Weâll certainly make sure this wonât happen for 13.
2 Likes
No disrespect to the creators, but IMHO a software release such as 12.0.0 with two zeros in its version number, canât be as stable as itâs predecessor. If stability is such a concern, then wait for a maintenance version, or test & stage your upgrade to 12.0.0.
why that? It is a number and it all depends on the process what the number means. The issue I see here is that it looks like there are release channels but it is not possible to get which version is in which stage.
And that 12 is stable although there are issues is a marketing issue imho. The press was told it is being released and it was not possible to postpone the official release afterwards because people expect to get version 12.
All previous beta versions are not rolled out to customers. And if the user base is much wider, some more rare problems come to the surface. Many apps are developed by the community, some apps, which might be important for you, are not ready for the new version. A bug in NC 12 would be this one here: [stable12] Prevent sending second WWW-Authenticate header by LukasReschke ¡ Pull Request #5386 ¡ nextcloud/server ¡ GitHub
You can do the same for other systems. Debian/Ubuntu release a new version but offer an upgrade only after the first point release (unless you force it yourself).
If you want to help the project and you want to be sure it is running well in your environment, use a similar test setup and test the beta version and release candidates.
It wasnât really postponed, it was never planned to push the upgrade to everybody at once. However the process should be clearer that people know what to expect. Perhaps in the release notes or at least a sticky topic here on the forum.
From my point of view it makes sense to announce a new version once it is being planned to push it out to all customers.
Have a look at the number of fixes for 12.0.1 compared to other maintenance releases.
This is very weak.
Month after official release still asking the users for help. Mark it as beta next time or wait with the rollout and announcement, please.
ummm⌠if something like âhelp test nextcloudâ or
To test the upgrade to 12.0.3RC2
(see text of thread)
appears - this is a clear sign thatâs still not a productive version and thus NEEDS to be tested.
how else than by user-testing would this be possible?
plus: you arenât forced in any way to install it - itâs not in the release channel, yet.
so what was your point?
@JimmyKarter: You mentioned very good points 
But it canât hurt to add beta in addition to the warning signs you listed.
Like this it becomes even more evident.
So why not just add the label?
if RC2 doesnât mean: still beta and not productive?
for me itâs enough to make sure staying away from it until itâs released. but wells⌠thatâs just MY point of view.
Okey. Again you have a good point :))
With RC, a beta is not needed.
1 Like