Just to be clear, why we are reluctant to do it. There are configuration changes in hostapd and to support them we would also have to pull latest netifd and because of that latest luci and latest dependencies of those packages. The format of those packages with Lede project were changed so they are incompatible. This pretty much is not pull two packages but pull around few hundreds of them and rewrite their makefiles while breaking rest of the system. Pretty much impossible. The way we are currently approaching it is to have 4.0 ready as soon as possible instead of sinking hundreds of hours in to the dying fork. I am not saying that I am happy that we have old packages in our repository but we have to see bigger picture.
Understood. But just to be clear about the user story (although that doesn’t change anything from your point of view): it’s not just about updating old packages (like you stated on gitlab) but about missing functionality and security fixes!
That is all well and appreciated but the issue is only that TOS4.x is repeatedly cited/advertised as being the cure whilst it is still in the alpha stage and there are only vague hints that it may arrive production ready till end of this year, implying uncertainty that this will be achieved.
Almost 1 year ago it was stated that TOS4.x would be eventually in beta by end of 2018.
Certainly the dev team is doing as best as they can but that developers have departed and not being replaced, plus at the same time adding the MOX workload, in all likelihood has not aided the pace of development and the consequence is that users ultimately paying the price as being a in limbo between out of date core components with the LEDE repo and some alpha state that is still facing all king of issues on its own in the TOS4.x trunk.
Have some developers left the team?
Can the latest version of nextcloud 16 be packaged for tos?
Yes, Nextcloud 16 will be in Turris OS after some testing.