llama.cpp
llama.cpp copied to clipboard
ggml-org
Too many releases
Every second entry in my timeline is a new anonymous, automatical release of this project, please only post releases less frequently...
Somehow in my view it's better to keep more releases so we can figure out where the problems coming from.
IMO we should come up with an alternate method of distributing binaries. Specifically:
- the automatic releases pollute home feeds with not-terribly-useful information
- they also require making a bunch of tags that clutter up git pulls
- keeping binary artifacts around forever means people may accidentally download an old version without realizing it (since releases are not sequentially named)
- we only distribute Windows binaries, and not ones for other OSes
That said, there is definitely significant usage of the prebuilt binaries (30ā400 total downloads depending on the commit), but I am of course unable to tell how much of that download traffic is automated vs real people.
I think there should be a place where there is always the newest binaries only and there is no point in having a release for every single commit. There is a commit history for that.
It's really hard to say nicely how much I hate the basis of this issue. If you don't want updates, don't follow the project. If you want to follow, but not be notified of releases, then it's your responsibility to set it as such: https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository
The project shouldn't have to suffer because of unset custom follow settings. The feed is full of what you've requested it be filled with. There should NOT be delays in releases on the basis of a cluttered feed, that's a user issue not a CI one. Stretching out releases will only hamper development efforts, and make it that much harder for someone to easily download and run various [and especially the newest] revisions.
Re @j-f1:
keeping binary artifacts around forever means people may accidentally download an old version without realizing it
I disagree as I've never had that issue. Also, the latest release is always marked as such, along with a timestamp and brief description. If that weren't the case, I could understand a small confusion specifically when trying to download an older version.
That's what I have been doing as well. If it is simply an issue that people aren't aware that it is possible to disable notifications about new releases, I agree that there is no need to change anything. Having frequent releases allow us to receive more feedback.
I wasn't aware one can disable release notifications separately. If so - then it is not an issue
@j-f1 I recommend you send feedback for the beta feature you're using in that case, especially if you've set custom notification settings already.
For me seems the feed comes from starring the project, you can also try clicking the 3 dots and telling github to not notify you so much š
It's really hard to say nicely how much I hate the basis of this issue. If you don't want updates, don't follow the project. If you want to follow, but not be notified of releases, then it's your responsibility to set it as such: https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository
The project shouldn't have to suffer because of unset custom follow settings. The feed is full of what you've requested it be filled with. There should NOT be delays in releases on the basis of a cluttered feed, that's a user issue not a CI one. Stretching out releases will only hamper development efforts, and make it that much harder for someone to easily download and run various [and especially the newest] revisions.
Re @j-f1:
keeping binary artifacts around forever means people may accidentally download an old version without realizing it
I disagree as I've never had that issue. Also, the latest release is always marked as such, along with a timestamp and brief description. If that weren't the case, I could understand a small confusion specifically when trying to download an older version.
The thing is, I want to be notified when there are major releases! But not on every 2 lines changed somewhere! Sure, I could unfollow and whatever but I think it is my good right to communicate the fact that I want to be notified on major releases and not on every single damn commit, sorry.
The thing is, I want to be notified when there are major releases!
hackernews will do that for you :laughing:
Maybe instead of tagging every commit as a release, make weekly release tags and mark the release for each commit as a pre-release. Then once notifications for pre-releases can be hidden, this issue should be solved.
