Announcement

Collapse
No announcement yet.

HUG DAY! Help make Feisty a solid release!

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    HUG DAY! Help make Feisty a solid release!

    ~ Anouncement! ~
    Kubuntu Desktop Bugs Week
    See third post below. Sorry about the very late notice, but the forums were down. You can still come and help!
    -----------------------------

    Next Wednesday, March 7th in all timezones (and really every wednesday and every day! ), is a Ubuntu Hug Day!

    This is a very special Bug Day: on Hug Day, when someone closes a bug, then someone else should hug him/her. Why? This is a very special way for us to tell everyone that we love contributions! And triaging bugs is a really big contribution.
    There are currently 23000 open bugs in Ubuntu. 2000 are in Kubuntu/KDE. Of those, half are unconfirmed and really need your attention!

    This may seem a little overwhelming at first, but if we get people working on triaging, we CAN get all the bugs organized and fixed. It's only impossible if we leave the small group of developers to do all the work, most of which involves no development. Every bug triaged is a step toward a quality stable release. Everybody can help -- all you need is to be an enthusiastic user of Kubuntu (and to follow the Code of Conduct).
    We have about a month and a half until Feisty is released, so it's prime time for fixing bugs. This is why you are a Feisty Testing user, right?

    Come help any time! Read the wiki page, get on #ubuntu-bugs on freenode on IRC, and get to the Kubuntu bugs!
    Blog
    Tags: None
    • Top
    • Bottom
    #2
    How to triage effectively

    What does triaging bugs mean?
    • Responding to new bugs as they are filed.
    • Reproducing and confirming bug repots.
    • Asking the reporter to provide missing information.
    • Searching for duplicates in the bug tracking system.
    • Sending bugs to their upstream authors, when applicable. For KDE this is http://bugs.kde.org
    • Cross-referencing bugs from other distributions.
    • Classifying bugs by package.
    • Prioritizing bugs.
    • Expiring old bugs.


    Suggestions and rules:
    • Read the wiki pages:
      • https://wiki.ubuntu.com/UbuntuBugDay
      • https://wiki.ubuntu.com/HelpingWithBugs
      • https://wiki.ubuntu.com/Bugs/HowToTriage
      • https://wiki.ubuntu.com/BugSquad
      • https://wiki.ubuntu.com/Bugs/Responses
    • Be polite!
    • Unconfirmed bugs are a priority. An unconfirmed bug isn't of much use to a developer or to the reporter. It's a waste of developers' time to try to figure out if things are even real bugs, so that's our job. Do your best to reproduce bugs so that you can confirm them.
    • Bug reports often lack essential information required to fix them or to find out if they are already fixed. This can range from basic information such as what release they are using or even what program the bug is in to slightly more complex things like stack traces for crashes. Ask the reporter for any missing information. Be clear and polite. When you ask questions, mark the bug status as "Needs Info" until all the required information is provided. If you can reproduce the bug, provide the information yourself and mark "Confirmed."
    • Duplicate bug reports are common. When you are looking at a new bug, open up another window and do an advanced search for similar bugs, including ALL bugs -- closed and open. If you are certain a bug report is a duplicate, mark it that way and comment on the bug to inform the reporter. Usual responses for this can be found here. Other than this, avoid commenting on bugs marked as duplicates -- comment on the root bug.
    • Many bugs have already been fixed. For older bugs that you cannot reproduce, ask if the reporter is sill having the problem. If the problem was fixed with an update, you can close the bug ("Fix Released").
    • Bugs that are marked as "Needs Info" for over 3 months with a clear request for information but without a response that you can't reproduce aren't particularly useful. They should be "Rejected." When closing a bug for this reason, be polite and inform the reporter why you are closing it, and tell them that they can reopen the bug if they still have the problem and can provide the needed information. Some responses for this can be found here.
    • If you think a bug is in KDE and not Kubuntu specific, please search for it at KDE's Bug Tracking System and file one there if need be. Link the upstream bug in the launchpad bug by clicking "Also Effects Upstream." A bug with an upstream report should usually be Confirmed (you often shouldn't file it upstream if it's not). These bugs probably won't get fixed for Feisty, but can do a lot to improve the next version of KDE.
    • Pick an application that you use a lot, and concentrate on it. This helps narrow down the list of bugs you are looking at and makes the work much more manageable. It also helps to be knowledgeable in the program(s) you are doing bug work for.
    • If you have some rare configuration, look at bugs relating to it. For example, if you have a dual monitor setup, try to confirm some xinerama related bugs. This is particularly helpful since many other people who come across those bugs have no way of doing anything with them.
    • Keep all this in mind when filing your own bugs.
    • Don't confirm your own bugs.
    • Don't duplicate efforts. If there is already someone working on a bug and asking the right questions, move on to another one. There are plenty to go around.
    • There's a nice bug statistics page that shows open and unconfirmed bugs over various periods of time. If you make a visible dent in those graphs, feel proud: you've done an excellent job helping Kubuntu. Be sure to get your well deserved Hugs!
    • Keep in mind that while closing bugs is important, the key is that the bugs are FIXED.
    • DO get on #ubuntu-bugs if you need help, to discuss bugs, and to watch for incoming bugs. #ubuntu+1 can also be useful to discuss Feisty problems with other users. Don't use #kubuntu for this.


    FAQ
    Why can't I change the importance of bugs?
    You need to be a member of the ubuntu-qa team on launchpad to change the importance of bugs. This is mostly so people are responsible and don't raise the importance of their own bugs. See https://wiki.ubuntu.com/UbuntuQA for more information.

    Other useful information
    It helps to know what's in what package. Some useful specifics (areas with common mistakes) for KDE:
    • The displayconfig, mountconfig, serviceconfig, userconfig, and wineconfig settings modules and powermanager are in kde-guidance.
    • Konqueror, Kate, Konsole, and Kicker (and more) are in kdebase.
    • Ark is in kdeutils.


    Happy bug hunting!
    Blog
    • Top
    • Bottom

    Comment

      #3
      Re: HUG DAY! Help make Feisty a solid release!

      ~~~ ANNOUNCEMENT ~~~
      We are having a week of bug triaging focusing on Kubuntu Desktop applications, inspired by a similar effort by the Ubuntu Desktop Team. Every day the week of Monday March 12 through Friday March 16 we will pick a major application/package in the Kubuntu Desktop and triage (and maybe fix!) as many of its bugs as we can. With enough people helping, we can get all the bugs in major desktop components sorted out and fixed.

      Everybody can help!

      More information, tasks, bug lists, and a schedule are here:
      https://wiki.ubuntu.com/KubuntuTeam/Bugs

      The how-to above is there too, so please read that page and stop by #kubuntu-devel and #ubuntu-bugs on IRC and help out!
      Blog
      • Top
      • Bottom

      Comment

        #4
        Re: HUG DAY! Help make Feisty a solid release!

        From this week's Ubuntu Weekly News
        Ubuntu Hug Day now every Friday!
        Ubuntu Bug Squad will be holding the first of what will be weekly Hug Days on Friday, March 23rd. This also follows the Beta release of Feisty Fawn scheduled for the 22nd. So on 23 March 2007, in all timezones, we'll be meeting in #ubuntu-bugs on irc.freenode.net for another Ubuntu Bug Day.
        Blog
        • Top
        • Bottom

        Comment

          #5
          Re: HUG DAY! Help make Feisty a solid release!

          Originally posted by GameManK
          ~~~ ANNOUNCEMENT ~~~Everybody can help!
          Would if I could understand the language
          Just wanted to say, though, that I installed Feisty Beta 7.04, or rather used the upgrade tool to upgrade 6.10 which is running on an external USB disk. Apart from it deleting ipodder and NVU, and swapping over a couple of USB disk designations, that has confused some software, it went very smoothly. Whoever wrote this did a great job, thanks. Greg
          HP Pavilion 40GB/512MB hence external USB disk
          • Top
          • Bottom

          Comment

            #6
            Re: HUG DAY! Help make Feisty a solid release!

            Just got this announcement:
            Originally posted by Daniel Holbach
            Hello Ubuntu Lovers!

            Feisty Fawn Beta is now released and everyone has done a great job. Lots
            of people work within the Ubuntu BugSquad [1], some of Ubuntu's teams
            have set up weekly bug goals [2] and everybody is trying to get as many
            bugs fixed as possible for Feisty. If you ever wanted to get involved,
            this is the perfect time to get started. We're having a HUG DAY!

            [1] http://wiki.ubuntu.com/BugSquad
            [2] https://wiki.ubuntu.com/DesktopTeam/BugState


            We will try to triage as many bugs as possible, but specifically look
            into the targets outlined at
            http://wiki.ubuntu.com/UbuntuBugDay


            Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go
            there every other day too!

            When to join the Hug Day? Next hug day is on March Friday 30th, 2007 In
            all timezones. But again, you can go there every day and help with
            triaging the bug tracking systems.

            We can't stress it enough: everyone can help. So join us for the Hug
            Day!

            Make a difference: join the Bug Day on Friday, March 30th. We will be in
            #ubuntu-bugs (Freenode) all day and night, and will be ready to answer
            your questions about how to help.

            If you're new to all this, head to
            http://wiki.ubuntu.com/HelpingWithBugs

            Have a nice day,
            Daniel (for the BugSquad)
            Blog
            • Top
            • Bottom

            Comment

              #7
              Re: HUG DAY! Help make Feisty a solid release!

              Originally posted by gregb49
              Would if I could understand the language
              What is your native language? Sounds like you're interested in helping out. If so, I'm sure there's some translation to do.

              Or did you mean you couldn't read the post for some reason?
              Blog
              • Top
              • Bottom

              Comment

                #8
                Re: HUG DAY! Help make Feisty a solid release!

                should have stickied this one way back, it is now if there are any future Hug days coming up
                • Top
                • Bottom

                Comment

                Previous template Next
                Working...
                X