Replies: 2 comments
-
While I'm not against this idea per se, I think they actually don't want to do this purposefully, so that they don't have tons of beta or even pre-beta versions of the patch floating around everywhere mucking up things. |
Beta Was this translation helpful? Give feedback.
0 replies
-
There's a PR for it: #929 Github doesn't retain the artifacts for too long, so having releases available would make it a lot easier to test older versions. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First of all, thank you for your great work on this project.
I would like to suggest publishing pre-compiled binaries as official GitHub Releases on a regular basis.
Motivation:
For users who are not developers or are not familiar with the compilation process, it's currently difficult to use the latest version of the software. Similarly, for users like myself who don't actively contribute to the development, setting up the specific (and sometimes outdated) build environment and toolchain just to get an executable can be a significant barrier.
This means that many potential users are unable to benefit from the latest features, bug fixes, and improvements.
Proposed Solution:
Publishing a pre-built version periodically (e.g., monthly, quarterly, or after a set of significant new features) would make the project much more accessible. This would allow a wider audience to easily download and use the software without needing to compile it from the source.
This would significantly lower the barrier to entry and likely increase the user base of the project.
Thank you for considering this request!
Beta Was this translation helpful? Give feedback.
All reactions