On Mon, 27 Jan 2020 at 09:37:28 +0100, 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
>
Well that is another problem, and probably users will use the nextcloud update
and this will also end up in a problem on our next release, but I think every
user is a different world so...
--
- gonzalo
