On 9 July 2011 17:40, Larry Finger
Rob OpenSuSE wrote:
So rather than shipping the latest automatically, have some quality control!
I got a little behind in this thread, and will try to catch up now.
There is no intent to "fool" the users. If I did not think that MS6 were fully qualified to be called a "beta", then I would not have proposed this. In fact, if it is not, then openSUSE is doomed. A reputation for releasing buggy code is impossible to shake.
The scheme proposed by M. Raiko is not that different from what happens in the kernel. Anything not available by the end of the merge period has to wait for the next cycle. If openSUSE used that scheme and froze features/versions after MS2, a lot fewer bugs would make it to GM. I'm not sure that I want to go that far as we would be shipping some really old stuff. Perhaps the rolling releases of Tumbleweed will help debug many of the updates that will be in our next release.
A distro is different, because it compiles and serves in conveient form for most part the output of upstream. Rules about freezing features & versions, are inherently broken. It's intelligent pragmatic decisions that are needed not rules that appeal to bureaucrats. For instance are upstream fixing bugs and adding small features or redeveloping the whole project etc etc. Is the project directions suitable? Project should ship the best software it can, and think ahead a few months beyond release day to. Rob -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org