On Fri, 2014-11-21 at 00:47 +0900, Fuminobu TAKEYAMA wrote:
Oh well. It's nice to see the same discussion at every release: - before the release: "Can we do the freeze later?" or "Can I have a freeze exception for $whatever, please?" - after the release: "We need a longer freeze and more testing"
Do you see the pattern? ;-)
That's a typical pattern :-)
But the package was not in that pattern. Its maintainer and reviewers determined that the update should be just a bug fix update. (Actually, the update contains a new feature interacting with an application from another package)
We had one release with 7 betas (or more? Bugzilla lists up to 9 betas and 5 RCs) some years ago[1]. Believe me, you DO NOT want that - having that many betas or RCs means you had lots of bugs to fix, and probably have more left than in two "quick" releases ;-)
Now we have Tumbleweed and openQA. So we maybe can use RCs to fix more minor bugs than ever, I think. If the release schedule is fixed, the number of RCs will not be a problem.
Fuminobu TAKEYAMA It's a common pattern for the simple reason that there is plenty of discussion, but no action.
This last release cycle we were good with action on openQA and such. I think we need to focus on retooling our collaboration infrastructure so we can better deal with these various things. The other point for working is that we need to have better marketing communication of changes. I've found that our Google+ page seems to be our most powerful marketing and information tool. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org