When we package software without a stable release yet and active development, we could update the package after each commit, which could happen multiple times a day.
That seems not to be useful as it costs time to update, verify and build.
What should be the criterias to update such a package?
I think the changes should be significant for the user (new features, bugfix that affects the users) or it hasn’t been updated in some time (like a month).
I’m a maintainer of bcachefs and @eadwu has done very frequent updates lately. That’s why i came up with this topic.
I’m not sure if anyone actually uses the package and if it is worth the effort.
What do you think?