Replies: 1 comment
-
|
hey @wszgrcy I love this and I'm all for it. The only reason this is not happening (yet) is that sometimes the features grouped together are better. I'll release a new perry version once a day manually for now, does that sound good to you? Long-term this is the goal though! Other problem why this is problematic right now: Github gives us only so many workers and they are not the strongest. Better would be if we had our own workers or pay for it but that's an actual expense (and not cheap with our volume lol). |
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.
-
Thank you for developing this project. The development pace has been impressive so far, and issues are being resolved promptly. However, I’ve noticed that releases aren’t automatically published upon each commit. This means that after an issue is fixed, users might have to wait a considerable amount of time before the new version becomes available.
Would it be possible to implement automatic release generation similar to
llama.cpp, where a new version is published every time a commit is merged? This would make testing much more convenient. If building takes too long, you could also consider scheduling automatic builds at regular intervals (e.g., every X hours).Beta Was this translation helpful? Give feedback.
All reactions