On 2021/02/24 14:21, Landry Breuil wrote: > 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 ?
I don't think we can, really... Would it make sense to have a couple of versions in ports? Say nextcloud/20, nextcloud/21 Initially have an upgrade path via @pkgpath from www/nextcloud to www/nextcloud/20, then at some point after release (maybe when 22 is out) remove /20 and add an upgrade path to /21. That way people running pkg_add nextcloud get a choice, they have an upgrade path that's still valid with upstream, and if they're running 20 and want to move to 21 before the port upgrade path is adjusted they can just pkg_delete + pkg_add.
