On 1/28/20 1:25 AM, Stuart Henderson wrote: > On 2020/01/27 09:37, Landry Breuil wrote: >> On Mon, Jan 27, 2020 at 08:59:55AM +0100, Gonzalo L. Rodriguez wrote: >>> On Sun, 26 Jan 2020 at 09:59:42 +0000, Alessandro Grassi wrote: >>>> Greetings, >>>> >>>> the nextcloud version in /packages for 6.6 is 16.0 on FTP, while the >>>> version in /packages-stable is 18.0. A bump of 2 major releases feels a >>>> bit too steep for a stable channel. >>>> >>>> For what I can tell, fixes are being applied upstream to older releases as >>>> well. >>>> Is there any reason why the new major is being pushed rather than the new >>>> minor release? >>>> >>>> Regards, >>>> Alessandro >>> >>> Hello, >>> >>> Yes, it was a bit too much, after talking with sthen@ I will try to >>> separate the >>> versions on -current and -release, probably with different branches as we >>> do on >>> another ports. >> >> You'll also have to make sure for how long 'stable branches' (and how >> many) are maintained upstream.. cf >> https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule >> on 6.6, if 16.x is unsupported upstream after a while, do you prefer >> jumping to 17.x or staying with an unsupported version ? :) >> >> Landry >> > > That is one of the factors to consider when deciding when to update to a new > major in -current :-) >
To be honest, upgrading from a minor or major version of nextcloud (assuming you follow all updates) gives generally the same update problems (if you have some, which I do). So I feel it's better to follow upstream closely than to stay on older versions. This is of course valid for nextcloud but not for most of the other ports.
smime.p7s
Description: S/MIME Cryptographic Signature
