Update versions of supported Nextclouds apps in our system requirements

[lindenthal]

Our system requirements were outdated after two new versions have been released.

[lindenthal]

Hi @wielinde,

I would like to discuss and decide with you whether we support old versions as soon as new versions were released.
Additionally I would like to decide with you on a plan on how new releases are installed and tested on our side. This is also something we need to discuss and decide together with the openDesk team.

cc @dominic-braeunlein @NobodysNightmare

[NobodysNightmare]

For our integration_openproject app I see that we should bump the required version quickly, but that's an easy call because we are in charge of releasing it, so we know that it was released and before the release we checked compatibility and also have a general idea which changes could impact compatibility.

For apps like "Team folders", but also others that we may depend on (oidc, user_oidc), the situation is not as clear for me to be honest. When a new version of a third party app is released, we might not notice at first. Even if we notice, we don't know whether the new version will behave better or worse than the old version w.r.t. OpenProject compatibility.

As an aside illustrating part of the problem: In the meantime of opening this PR, 19.1.0 is not the latest version of team folders anymore, but 19.1.1 is.

So what is my suggestion? I think the least that we should do before declaring that a newer version is required is performing tests with the newer version (QA), but probably also read changelogs if they are available to get an idea whether any of the changes is relevant for us. I.e. one approach is experimentally confirming compatibility, the other is theoretically confirming it. Since this is work, I'd suggest to not actively do it with every release of third party software, but rather add a periodic process on our side. E.g. assuming that QA is already testing the integration ahead of every OP release, it might be sufficient to ensure that these dependencies are updated to their latest version as well during the corresponding smoke tests. Then we'd confirm new versions roughly once per month.

[wielinde]

@lindenthal @NobodysNightmare We need to be careful here to not raise the bar higher than normal Nextcloud standards. AFAIK at Nextcloud there is a difference between providing a SLA and actually ensuring (by QA/CI/...) that a certain version is working.

On practicality:

• We always bump our Nextcloud app to the latest version. We don't support older versions of the app. We always wanted to only have one app supporting multiple Nextcloud versions at the same time so that we can reduce release complexity.
• When it comes to other apps like oidc, user_oidc etc I suggest that we communicate the lastest combination of app versions that we have successfully tested.
• Ideally we don't provide work arounds in our code for issues that stem from Nextcloud or their supported apps but rather support Nextcloud to fix those on their end.

[wielinde]

@lindenthal @NobodysNightmare On the matter of automatic QA of integrations I propose we work closely with what openDesk has already in place and extend it only when and where needed. That way we could consolidate automation around openDesk.