https://bugzilla.novell.com/show_bug.cgi?id=408252
User alberto.passalacqua@tin.it added comment
https://bugzilla.novell.com/show_bug.cgi?id=408252#c121
--- Comment #121 from Alberto Passalacqua 2009-01-23 07:16:10 MST ---
@Michael Meeks: you are in part right with your point about testing. But
honestly i do not think that community testing can replace at least a basic
internal quality assurance. This issue as various others in openSUSE 11.1 are
of such a bad level that should have been found during an simple run of
internal test cases. I'm speaking of this problem, of huge memory leaks in
beagle, of X instabilities and system freezes at boot or after some days of
operation. For these problems you, Novell, can't simply rely on the community
and think for good. The community is simply not prepared, and not big enough to
do that. Moreover learning is not easy because the documentation on the wiki is
missing, which makes the learning process too steep and long.
What you are asking (running alphas) is not possible for many: our alpha
releases are not usable for everyday use, and in most of the cases they are
barely instalallable. In the current situation the most you can expect is some
testing in virtual machines of the early pre-release versions and some testing
of the final steps (RC) on real hardware by some users with a certain
experience. From this to hoping they will find bugs as in systematic testing,
there is a huge difference, and systematic testing of key elements is hardly
doable at a community level, at least if not coordinated and planned in some
way.
I think one big change is necessary if you want to rely on the community so
much, which is a complete revision of the patch policy. OpenSUSE is still tied
to the obsolete idea of releasing security only fixes, which is OK if the
initial release is of good level. This has not been not regularly happening
since openSUSE was started, and we had often had releases that in principle
could be fixed and improved significantly with a relatively small number of
updates, which were not done at all, or not done timely, left to wait for
approval for months, with the result that users left or were very frustrated.
If this is not going to happen, we will always have releases full of problems
for their whole lifecycle, and unhappy users.
@Karsten Konig: the discussion started here. I know it is off-topic, that it
might not be the right place, but for once nobody will suffer for a few post
that eventually might bring to a solution to avoid these issues in the future.
So, please, be patient. Moving it would mean losing the context, and probably
also part of the participants.
Regards,
A.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.