Repository navigation
SourceForge or GitHub preferred for releases? #1631
|
The Buzz readme on GitHub currently recommends getting the macOS and Windows releases via SourceForge. What is the reason for this, as opposed to obtaining them via GitHub? |
Replies: 1 comment 1 reply
|
Github has some file size limits, so current Windows builds can't be one file, some users have missed instructions to download all three files, so with no .bin files the installation fails for them. On Sourceforge we get one zip and a bit less explaining is needed. Mac versions for future releases will not have version for intel macs, we have dropped support for those, so pointing users to Sourceforge will have all supported versions for Macs in one place. Apart from this versions are exactly the same and users can also get them from releases, but if we recommend some one location, Sourceforge has minor benefits. |
Github has some file size limits, so current Windows builds can't be one file, some users have missed instructions to download all three files, so with no .bin files the installation fails for them. On Sourceforge we get one zip and a bit less explaining is needed.
Mac versions for future releases will not have version for intel macs, we have dropped support for those, so pointing users to Sourceforge will have all supported versions for Macs in one place.
Apart from this versions are exactly the same and users can also get them from releases, but if we recommend some one location, Sourceforge has minor benefits.