On Wed, Feb 24, 2021 at 01:39:15PM +0100, Stefan Sperling wrote: > On Wed, Feb 24, 2021 at 10:04:05AM +0100, Gonzalo Rodriguez wrote: > > Yes, this is for -current users > > > > — gonzalo > > I think Johan is suggesting that 6.9 should be shipped with Nextcloud 20, > not Nextcloud 21. And right now, "6.9" means -current. > > Otherwise people upgrading directly from OpenBSD 6.8 to OpenBSD 6.9 would > skip an intermediate upgrade to Nextcloud 20. Skipping a release is not > recommended by the Nextcloud team. > > If Nextcloud 21 is committed after 6.9 then users will upgrade like this: > OpenBSD 6.8 (NC 19) -> OpenBSD 6.9 (NC 20) -> OpenBSD 7.0 (NC 21) > Instead of: > OpenBSD 6.8 (NC 19) -> OpenBSD 6.9 (NC 21 maybe cannot upgrade from NC 19?)
that cant work on the long run i think, as nextcloud major releases arent fully synched with our 6 month release scheme, cf https://en.wikipedia.org/wiki/Nextcloud#Release_history and https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule eg if 7.0 ships with 21 but the upstream last release is already at 24 or something .. we'll never catch up. As 21 was released upstream, 18 was EOLed. on the other hand, can we *expect* ppl running 6.8 to update via packages-stable to make sure that they go from 19 to 20 via -stable ? Landry
