Fix the GitHub release pages

[Sukiyucky]

Release candidates and releases on the GitHub Release page do not always have the installer executable for people to download. Only the source.

You need to make the installer executable available so that people can roll back to a previous version. And without an installer package, how do you expect people to even test release candidates and flush out bugs? Surely, you can't expect users to download Microsoft Visual Studio and build it.

Go to every release/release candidate and click on the Assets dropdown to see what I mean:
https://github.com/obsproject/obs-studio/releases

 

[R1CH]

If you're referring to 24.0.5, this is a Mac only release to fix issues with Catalina.

 

[Sukiyucky]

No, not 24.0.5.

If you go down the list of all the releases, some have installers, some don't.

For example, for version 24.0 there is this under the Assets drop down, source code only:

I went manually through GitHub on the last few releases and see this:

• 24.0.2 has no installer, only source
• 24.0.1 has no installer, only source
• 24.0 has no installer, only source
• 23.2 has no installer, only source
• 22.0. release candidate 2 has no installer, only source
• 22.0 release candidate 1 has no installer, only source
• etc.

So for example, users who are having problems in 24.0 and need to rollback to 23.2 have no way to do so.

 

[dodgepong]

Because they would roll back to 23.2.1.

If a release is missing its installer, it's because it was pulled due to something being broken, and thus needing to be hotfixed. We don't want people running 23.2. If they want to roll back from 24, they should use 23.2.1. Same story with 24: the canonical "24" should be 24.0.3, not 24.0 or 24.0.1 or 24.0.2.