Home Home > 2008 > 05 > 19 > openSUSE Wants Your Vote (on Bugs)
Sign up | Login

openSUSE Wants Your Vote (on Bugs)

May 19th, 2008 by

Attention openSUSE users and contributors! It’s time to exercise your vote and help the openSUSE team identify the bugs that need to be squashed prior to the openSUSE 11.0 release. On May 22nd, we’re having a bug voting day to help ensure we identify the most troublesome issues in Bugzilla under openSUSE 11.0.

Please join us on Thursday, May 22nd from 07:00 UTC until 19:00 UTC. Check out the voting instructions on the Bugzilla and openSUSE wiki. We’ll also have live help available in the #openSUSE-Factory channel on Freenode.

If you don’t have a Bugzilla account yet, you can sign up for one here. You know you want one! Sign up today!

By prioritizing the bugs, we can ensure that we’ve got the right bugs in our sights for the openSUSE 11.0 release.

Of course, you can help with bug voting at any time. There’s no need to wait for a bug day! Just roll up your sleeves and head over to the openSUSE Bugzilla and jump right in.

Questions or suggestions before the bug day? Drop me a note at zonker@opensuse.org.

Both comments and pings are currently closed.

28 Responses to “openSUSE Wants Your Vote (on Bugs)”

  1. HighwayStar

    Cyrillic in fb console bug posted half year ago and exist from 10.0 to 11.0 beta 3, but there are still no comments from mainteners.

    Russian users from #opensuse.ru channel still voted fr this bug but nothing changes, still no comments

  2. Wondering

    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? I think it really would be a better idea to fix all the bugs before the release – even if that might delay the release by a few days.

    • Beineri

      > 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? :-)

    • Unfortunately, yes — some bugs won’t be fixed. I don’t think any distro ships with 0 bugs, not if they’re being honest, anyway — but we want to identify the most critical bugs that need to be fixed before 11.0. Fixing “all the bugs before the release” would be next to impossible, I’m sorry to say.

  3. Yes I agree, thanks for this, lets hope most critical system and software bugs get fixed.

  4. fm

    It might be time for my one year old long time favourite:

    I gave up on it, but wonders may happen.

  5. andreas

    I have unfortunately still following problem with my TV card.
    This card does not work under Suse 11 beta 3. I hope that the final version 11 to end the problem with this TV card fixes. It is following chipset: Conexant CX23880
    This is the latest Version of Terratec HT PCI analog/dvb-T. (new Version MK II)

  6. Darkelve

    I would, but bug hunting (and especially, reporting) is hard for my non-developer brain.

  7. lukasz

    IBM R60 ATI mobility radeon x1400

    3D doesn’t work since 10.3 (10.2 OK) (Kubundu 8.2 Works 100% OK with 3d and ati-driver 8.4)

    KDE 4.0 totaly crashed after turn on transluent or any other effects (KDE4.0 BUG)
    KDE 3.5 Works GOOD, but without 3D

    suspand RAM OK
    suspand HDD OK

    Everything works good without any more configurations. Good JOB.

  8. Sergio1704

    How about having a list of release-critical bugs, like Debian, and not releasing before they are squashed? Why the hurry, anyway?
    10.3 was released with an extremely annoying bug: “Repair”, one of the features which made me a proud openSUSE user, didn’t work from the install media.

    • anon

      because that would be sensible, that sensible openSUSE is not. Just look at the anal reason for not waiting until 4.1.

    • Wondering

      I strongly agree to your idea of squashing all the bugs before the final release. I have one more suggestion. If at all openSUSE is bent of releasing it on-time(with some bugs) due to organizationsal constraints,I would suggest instead of releasing openSUSE 11.1(again with some bugs) – we can release openSUSE 11.01 with 0 bugs. Why cant we do that? Why cant openSUSE change the trend every other OS is following and produce a zero-bug OS. Let us call it openSUSE 11 (Zero Bug) – something like Ubuntu 8.04 LTS. I think that will really make the world look up to us… I dont know if this is possible. I am just a newbie. But I think, if this is done, there is nothing like it.

      • Beineri

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

        It’s not possible. You have no clue about software development.

      • Ryan

        No, I strongly agree with you. But Beineri is exactly correct. You have to keep in mind, who is Ubuntu committing to with Ubuntu 8.04 LTS? While Ubuntu is popular because it’s free, it doesn’t have the $$ numbers behind it – at least from real business partners. So, what does that mean? In other words, it means that “LTS” is nearly meaningless!!!

      • Ryan

        But, praise to Mark Shuttleworth (founder of Ubuntu). He’s a genius in his own work – love following him. I just like SUSE more.

    • Beineri

      > How about having a list of release-critical bugs

      Search Bugzilla for bugs marked as “Blocker”.

      • Beineri

        Actually querying Bugzilla for “SHIP_STOPPER+” flag is more accurate.

  9. Wallacy

    I installed the kdevelop4 by yast and he found the oxygen-icon-theme as a dependency! WTF?

    • Beineri

      Let’s ignore that KDevelop4 is not part of openSUSE 11.0, what’s wrong with that? It’s the standard/fallback icon theme of KDE4.

  10. Ryan

    For me, the most important bugs are already those listed under “Most Annoying Bugs” in about that order. I’m not expecting to install this on the ENIAC, or Konrad Zuse’s Z1 machine. And it’s truly a realistic disclaimer that not all OS’s work on all machines. Ubuntu flopped on my old Dell Inspiron 1100; whereas, my retail version of SUSE 8.2 (which is still installed) installed and runs beautifully. And the games are nice! I’m not realistically expecting SUSE to continue support for my old Inspiron, or every piece of hardware on the planet. I’m in disbelief that it supports as much as it does, which is extremely impressive. I have a computer science degree, and I’ll tell you, SUSE’s software engineers are doing a great job. They’re geniuses in my opinion. Wish I could do more testing for you.

  11. Sergio1704

    >Search Bugzilla for bugs marked as “Blocker”

    OK, thanks, but will 11 be released before all the “blockers” are squashed?
    10.3 was: “Repair” didn’t work.
    Honestly, sometimes I miss the old days, when the only way to get SUSE was buying a box. They were very few bugs and the boxes and their contents were so beautiful.

    • Beineri

      > 10.3 was: “Repair” didn’t work.

      AFAIK this regression was introduced as side-effect by a last-day fix of something other (means it did work all the time including last release candidates) and was only discovered after the ISO was sent to the DVD plant. So it was not a known bug like the others we are talking about here.

  12. David

    Here’s hoping that this bug gets fixed: 333753

    I’ve only been waiting since mid-october though, so who knows, but I can’t even install OpenSuse while this is still an issue!

  13. Ben

    I sure hope that we have a distrubution that ships with a working ipw or iwl driver for us intel 3945

  14. Be Fair

    I think we have to ask ourselves this question, “If this were a SLED release, will we release it with this number of unfixed bugs?”
    The answer will be a big NO.

    Isnt that unfair to treat a commercial release and a free release so differently in an open source project?

    • John

      I really do agree with you!!!

      It’s Unfair!!! I know it’s not possible to ship it with zero bugs… that is nearly impossible and would probably take a lot of months… (and there wouldn’t be possible to include recent versions of 3rd party software that were released in that “lot of months”) but one a-lot-more bug-free version would be for sure possible…

      anyway, i do think it’s a bit unfair… but i bet the developers are doing the best they can with the time Novell has given them… and for Novell… well they have to live on something… so… this schedules have to be used… it’s all part of the big machine… (even it it’s unfair, sometimes…)

      So, as far as i know… the things are in their best shapes…