Replies: 3 comments 7 replies
-
I agree apart from that maybe nightlies should be published after every pr. As that allows for testing and allow people that want to use the latest PR they can. |
Beta Was this translation helpful? Give feedback.
-
Our rule, as a project, is to release slowly and test thoroughly (as much as possible), to ensure we don't break the literally hundreds of thousands of installed users. It will be released when it's ready. |
Beta Was this translation helpful? Give feedback.
-
The counter goes up fast when refactoring and with automatic dependency updates. There's 163 PR's in the 0.15.0 milestone, 60 of which are made by Renovate (dependency updates) and 95 of which are mine. I haven't worked on much features, rather I broke the master branch for a while to refactoring a lot of code. Only recently (yesterday) I started to considered the master branch stable enough again for a next beta release.
We previously released at most once a year and this year we'll have 3 big updates, so we're already speeding up. Mind you, pretty much all changes come from one person (me) that works on Jellyfin in his spare time. |
Beta Was this translation helpful? Give feedback.
-
With 165 PRs in the 0.15 release milestone, I'd like to pose the idea of iterating faster.
Are there any current obstacles to releasing at a faster cadence to reduce the number of issues and features in a particular release candidate?
Beta Was this translation helpful? Give feedback.
All reactions