ES version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 323 words in the discussion.
Trending Topics
#tag#github#release#versioning#https#releases#com#ggml#org#create

Discussion (8 Comments)Read Original on HackerNews
More info about the versioning process is here: https://github.com/ggml-org/ggml/discussions/1579
seems like stray tags?
https://github.com/ggml-org/llama.cpp/commit/cea66f4c5a17255...
``` Add a "Create and push git tag" step to the release job, right before the "Create release" step. The tag is created with git tag and pushed with the deploy key already configured by the Clone step, instead of relying on the Releases API (action-create-release) to create it as a side effect.
The tag is lightweight, matching all existing b release tags. The step is idempotent: if the tag already exists (e.g. on a re-run), creation and push are skipped. ```
I think they just haven't configured the TAG part of that properly yet, so it created an incorrect tag the first run.
It's more reasonable for a lot of people to just follow master and build from source.
https://github.com/brian-learns/llama_cpp/blob/main/update.s...
No one seems to take it seriously, and why would my voice matter anyway? I think https://0ver.org shows us the industry doesn't really care about software versioning.
Hell, just drop the pretense and tell people to stick to commit hashes and dates.