When enough new features & bug fixes have accumulated in the development version. It’s the strategy I was using until now but it’s still somewhat vague. How do you determine when is this “enough”? Does anyone follow an objective rule for this?
Releases on a regular schedule (strategy of, e.g., R, Ubuntu, Firefox). All the projects I can think of for this strategy are very active projects with paid developers. This might indicate it’s better suited for this kind of project(???)
Whenever the maintainer has enough time to go through with the release process. I suspect this is a quite common approach but it is more based on constraints independent from the software and might not be what is “best” for the package.
I think this question becomes more pressing in the case of a low activity packages. With the 1st strategy, you run the risk of keeping features & bug fixes in the dev branch for a long time. But with the 2nd strategy, you produce of lot of small versions with few changes.
How do other developers estimate when a new release is due? Do you have tips or strategy to determine when the time is right?