Closed ann0see closed 3 years ago
What's the reason? I've not been following the macOS stuff.
The new build with Qt 5.15.2 supports macOS Big Sur without UI glitches and multiple small bugs but breaks compatibility to old versions of macOS. See: https://github.com/jamulussoftware/jamulus/pull/1687 and especially https://github.com/jamulussoftware/jamulus/pull/1768
Oh OK, so it's just a straight OS version split on the download page. I assume we therefore maintain two versions of 3.8.0+ from now on?
Just trying to work out what impact this has on what we say on the website.
I assume we therefore maintain two versions of 3.8.0+ from now on?
Yes. I think we could just link the legacy build from the macOS page the same as for the SourceForge mirror
How does that work with the links exactly then? Do we have two {{ site.download_file_names.mac }}
variables and change the SF link to point to the versions directory instead or something?
I think something like this would be enough:
So will we need to update these links for each release (until we abandon support for anything lower than macOS 11)?
Unfortunately yes.
But it's all in _config.yml
Ok. Just pushed this change to translate
@ignotus666 @jujudusud I also added the legacy link to your translations. You can translate them later on
Done for FR, to be merged.
We now provide two builds for macOS: legacy and the normal one. We should link both on the macOS page.