On Wednesday 10 of December 2014 03:41:19 Michele Calgaro wrote: > > I would suggest for patch releases not focus only on the number of fixed > > bugs. Substantial could be, for example, the importance of fixed bugs. > > Sufficiently frequent release of new versions also seems like a good card > > viability of the project. > > Agree as well. Anyhow substantial or major bug fixes would probably be > better done in minor releases, not in the maintenance ones. Or should be > incorporated in the maintenance ones only after a reasonable amount of test > time. IMO, maintenance releases should address bugs that do not require > major rework/changes. I think of them as a way to improve v14.0.0 without > major changes on it. > Instead I consider v14.x.0 releases at the same strength of the old KDE > 3.5.x releases. > > Just another 2 cents. > Cheers > � Michele I have a concrete example - bug 2222 - fortunately fixed before final R14.0.0. But imagine a situation that could not be fixed and now we should decide. I dare say that is certainly, it is a fix for very crucial issue. At the same time, in my opinion, this is not a fix that should mean release R14.1.0. For such a fix I would suggest release R14.0.1. And that's just the situation that I had in mind - a situation where, in my opinion, is inappropriate to wait for the completion of the specified number of patches for release. -- Sl�vek