github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-16 21:25:46 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4702] Introduce regular support releases #80642

New Issue
Open
opened 2026-05-09 09:15:26 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-09 09:15:26 -05:00
Owner
Copy Link

Originally created by @dcasota on GitHub (May 29, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/4702

The actual test case install base seems to be too small and bugfixes are recurring again and again

  • with Nvidia driver constellations
  • on single and multiple GPU installations
  • on platforms Windows/Linux on x86_64 and arm64 and on Mac
  • with version updates
  • ++

A regular support release model makes communicating accountability easier.

Introducing regular support releases e.g. for a lifetime of 6 months would help to refer to Ollama's accountability with respect to 2025++ plannings.

Originally created by @dcasota on GitHub (May 29, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/4702 The actual test case install base seems to be too small and bugfixes are recurring again and again - with Nvidia driver constellations - on single and multiple GPU installations - on platforms Windows/Linux on x86_64 and arm64 and on Mac - with version updates - ++ A regular support release model makes communicating accountability easier. Introducing regular support releases e.g. for a lifetime of 6 months would help to refer to Ollama's accountability with respect to 2025++ plannings.
GiteaMirror added the feature request label 2026-05-09 09:15:26 -05:00
GiteaMirror commented 2026-05-09 09:15:27 -05:00
Author
Owner
Copy Link

@Arcitec commented on GitHub (Jun 1, 2024):

Introducing regular support releases e.g. for a lifetime of 6 months would help to refer to Ollama's accountability with respect to 2025++ plannings.

Uhm. Your entire post begins by slagging off the project, calling it a buggy mess where bugs reoccur "again and again", and you then demand that they have "Accountability"? "Accountability and respect to 2025++ plannings"? Do you realize how rude and entitled you sound? There's not a single nice word in your post. Just insults and demands.

Ollama is a free MIT-licensed non-commercial project by a small company. They shall not be burdened by having to comply with other commercial companies rude wishes.

Having to maintain separate, "stable" versions is a major burden. And you just came here and insulted the project and then demanded "accountability", in one of the rudest ways possible.

Sorry for jumping in, but I am allergic to companies posting rude bullshit demands against free projects. I've seen it too many times, and have even been on the receiving end of these kinds of rude, entitled demands. You offered absolutely nothing but insults and demands, and some toxic corporate buzzwords. That is not the way to ask developers to do more free, unpaid work for you, man... If that's how you talk to your paid employees too, then I feel sorry for them for working in such a toxic environment.

What I would say, however, is that Ollama could decide to offer PAID support contracts for X months. That's the only way I see this request (lots more work) being fair in any way whatsoever.

<!-- gh-comment-id:2143219860 --> @Arcitec commented on GitHub (Jun 1, 2024): > Introducing regular support releases e.g. for a lifetime of 6 months would help to refer to Ollama's accountability with respect to 2025++ plannings. Uhm. Your entire post begins by slagging off the project, calling it a buggy mess where bugs reoccur "again and again", and you then demand that they have "Accountability"? "Accountability and respect to 2025++ plannings"? Do you realize how rude and entitled you sound? There's not a single nice word in your post. Just insults and demands. Ollama is a free [MIT-licensed](https://github.com/ollama/ollama/blob/main/LICENSE) non-commercial project by a small company. They shall not be burdened by having to comply with other commercial companies rude wishes. Having to maintain separate, "stable" versions is a major burden. And you just came here and insulted the project and then demanded "accountability", in one of the rudest ways possible. Sorry for jumping in, but I am allergic to companies posting rude bullshit demands against free projects. I've seen it too many times, and have even been on the receiving end of these kinds of rude, entitled demands. You offered absolutely nothing but insults and demands, and some toxic corporate buzzwords. That is **not** the way to ask developers to do more free, unpaid work for you, man... If that's how you talk to your paid employees too, then I feel sorry for them for working in such a toxic environment. What I would say, however, is that Ollama _could_ decide to offer PAID support contracts for X months. That's the _only_ way I see this request (lots more work) being fair in any way whatsoever.
GiteaMirror commented 2026-05-09 09:15:27 -05:00
Author
Owner
Copy Link

@dcasota commented on GitHub (Jun 1, 2024):

Hi @Arcitec,

70'000 star ratings of the github project, hundreds of forks and watches - these metrics reflects the circle achieved through the power of the developers.

In almost one year, 3'000 issues, 1'600 pull requests and daily commitments - the project owners were able to respond to requests for support and customizations. Quite a few volunteers started to support Ollama regularly by solving issues and contributing with pull requests. This makes the accountability higher than in many other open-source projects seen.

Unpaid care work is working hard. Whatever the product owners decide, I also believe that the developers have to be on this.

The increased number of open issues, 'it works in 0.1.xx but not in latest' and duplicates are indicators that the perceived responsibility has become self-evident for the users. That is the maximized executive power of Ollama. It's a recognition feature of the company.

The demand/supply momentum is crucial. What if users want to have more AI risk security features built-in, what if releases from market competitors run through more test cases automatically, what if users prefer other ideas like choice in ranked LLMs?

Every company has distinctive features that it wants to protect. Product owners are accountable for maximizing the integrity of the product ensuring from the work of the developers.

I share your concerns. The suggestion to introduce regular support releases is very direct, perhaps too direct and requires coordination. Scientific work is the basis for good products.

<!-- gh-comment-id:2143316699 --> @dcasota commented on GitHub (Jun 1, 2024): Hi @Arcitec, 70'000 star ratings of the github project, hundreds of forks and watches - these metrics reflects the circle achieved through the power of the developers. In almost one year, 3'000 issues, 1'600 pull requests and daily commitments - the project owners were able to respond to requests for support and customizations. Quite a few volunteers started to support Ollama regularly by solving issues and contributing with pull requests. This makes the accountability higher than in many other open-source projects seen. Unpaid care work is working hard. Whatever the product owners decide, I also believe that the developers have to be on this. The increased number of open issues, 'it works in 0.1.xx but not in latest' and duplicates are indicators that the perceived responsibility has become self-evident for the users. That is the maximized executive power of Ollama. It's a recognition feature of the company. The demand/supply momentum is crucial. What if users want to have more AI risk security features built-in, what if releases from market competitors run through more test cases automatically, what if users prefer other ideas like choice in ranked LLMs? Every company has distinctive features that it wants to protect. Product owners are accountable for maximizing the integrity of the product ensuring from the work of the developers. I share your concerns. The suggestion to introduce regular support releases is very direct, perhaps too direct and requires coordination. Scientific work is the basis for good products.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#80642
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?