Opensuse Wants Your Vote (on Bugs)

openSUSE bug voting day .... Please read:
http://news.opensuse.org/2008/05/19/opensu...r-vote-on-bugs/

Just a reminder that today is the bug reporting day for 11.0.

One can also go to IRC #openSUSE-Factory

500 Internal Server Error

The origin web server encountered an unexpected condition which prevented it from fulfilling the request. Please try your request again.[/b]

out of curiosity, is this not going too far? I mean whole bug voting thing? Why not vote for % of bugs left?
I would vote for 70% of known bugs left. I will be fun to install and see what new suse version is capable of (screwing).

Comment by Beineri
2008-05-19 12:43:34

> Do you mean to say that all the bugs that are identified(be it big or small)won’t be fixed before the final release?

Most of them not, correct. Or do you know any bigger software project that releases without known bugs? :-)
[/b]

same guy

Comment by Beineri
2008-05-20 07:44:07

> produce a zero-bug OS. I dont know if this is possible.

It’s not possible. You have no clue about software development.
(Comments wont nest below this level) [/b]

no idea who Beineri is.
nobody asks for impossible really (0 bugs: I think that user asked for 0 known bugs). But whole thing is useless. But he does not have clue about production either.
I understand if small things will not be fixed, but any known serious bug should be removed and whole ranging is simply silly. opensuse 11 will definitely have plenty of new unknown yet bugs to fix after release. Leaving known bugs unfixed really defies whole idea of upgrading.

nobody asks to fix unknown bugs, but if they do not plan to fix known bugs, then forget about upgrading.
There are still bugs open few versions ago.
Really, bad quality.

Why not vote for % of bugs left? ...
There are still bugs open few versions ago. Really, bad quality.[/b]

I've voted the past couple of years. Guess I mostly agree with your view, but I participate anyway as the current system is all we have. I don't think its totally useless, although I have wondered if my vote made any difference. I've also assumed that CRITICAL and BLOCKING bugs should given higher priority and must be fixed no matter what. ...

Should I waste my vote on those bugs? I decided not to, hoping common sense prevails. But there is definitely minimal to no guidance on this.

I played with 11.0 beta3 most of the morning/early afternoon (with KDE-3.5.9). zypper is very very fast. You might like it, and for the first time since 10.0, I'm thinking of leaving smart and going back to YaST software management (using zypper).

But the bug on the boot problem I am having is so severe, I'm very reluctant to install 11.0 beta3 (nor indeed install 11.0 GM) on any of my home PCs (other than my test PC).

Last time I tried to boot, it took me 14 tries before a successful boot. In addition to those 14, I've tried many more boot codes, to see if any would result in a successful boot. No luck. I hope they fix that bug. (I assume very few PCs experience this boot problem, else the community would be jumping up and down and complaining about 11.0 beta3).

what kind of boot bug is it that you have experience, oldcpu?

what kind of boot bug is it that you have experience, oldcpu?[/b]

I initially encountered it (or something very similar) in 11.0 alpha-3:
https://bugzilla.novell.com/show_bug.cgi?id=373012

That was closed, and fixed in openSUSE-11.0-beta2. Multiple re-boots works ok in beta2. But it was re-introduced in beta3:
https://bugzilla.novell.com/show_bug.cgi?id=392198

I've voted the past couple of years.[/b]

Anyway, I cast my vote. I'm a bit skeptical that it makes any difference ... but I cast my vote anyway.