Nextcloud 33 Appears on Git but Not Released - Any News?

[girish]

The .0 releases are always buggy. So, we skip those and wait for .1 . That also gives the nextcloud plugins some time to catch up with the latest release.

[sponch]

Please do not the same mistake as with 32. as seen some months ago many people here use nc in productive/business scenarios. So it should not matter to get an update 1, 2 or 3 months after release but to get it safely.

[jdaviescoates]

@sponch Cloudron can't test for every scenario.

Buggy releases and incompatible plugins are an upstream issue.

For critical production infrastructure I'd suggest it's possibly best to turn off auto updates and to update and test a clone before updating the production app.

[sponch]

@jdaviescoates said:

@sponch Cloudron can't test for every scenario.

Buggy releases and incompatible plugins are an upstream issue.

That's why they should wait with the release of new major releases.

[firmansi]

@sponch Still, the plugins can't be issues no matter the new major stable release exist, since the plugins not always part of NC , always test the plugins in clone one, before using in production version

[sponch]

It's not about any plugins but things like OIDC and overall stability that should be fine.

[jdaviescoates]

This post is deleted!

[jdaviescoates]

@sponch said:

That's why they should wait with the release of new major releases.

They do wait until the .1 - what are you asking for? For the to wait longer?

[sponch]

nope. just read my 1st post in this thread which refers to post 1.

[jdaviescoates]

@sponch I read it but I can't remember what happened (I don't think it effected me). What mistake was made?

[sponch]

@jdaviescoates https://forum.cloudron.io/topic/14339/nextcloud-update-pushed-too-early/22?_=1772614821048

[jdaviescoates]

@sponch thanks for the reminder