[Ubuntu Wiki] Update of "Bugs/Status" by es20490446e

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "Bugs/Status" page has been changed by es20490446e:
http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=63&rev2=64

Comment:
Asked users to only assign bugs just before starting working on them

  ## page was renamed from BugSquad/ManagingStatus
  <<Include(BugSquad/KBHeader)>>
+ 
  
  Bug statuses are a reflection of the current state of a bug report.
  
@@ -13, +14 @@

    * Bugs are submitted with this status,
    * They sometimes lack information '''and''' 
    * All of them should be untriaged
+ 
   * '''Incomplete''':
    * If you have to ask the reporter questions, set the bug to {{{Incomplete}}}
    * Ask the submitter to provide any necessary information in a comment, and make sure you subscribe yourself to the bug report so you will get any updates to the bug via e-mail.
    * <<Include(Bugs/Responses, , from="^== Incomplete bugs without a response from submitter ==", to="==")>>
    * If anyone, including you, comments on the bug, the 60 day expiration clock is reset.
+ 
   * '''Opinion''':
    * The status 'opinion' means there is a difference of opinion around a particular bug and people are free to continue the discussion, but the project or package maintainers need to move to other work and are considering the issue closed. The idea is that bugs can be marked closed, so developers aren't wasting time on them, but discussion can still be on-going.
    * This status 'opinion' is considered an experiment, and will be closely monitored.
+ 
   * '''Invalid''':
    * This status should be used when the bug report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter
    * This should also be used if the reported problem is not a bug at all, but for example user error
    * It should be used conservatively as bugs marked as Invalid no longer show up in default searches
    * Be sure to triple-check a bug before you invalidate it
+ 
   * '''Expired'''
    * This status is similar to Invalid, but is meant specifically for bugs that have been Incomplete for too long. (See above.)
    * This status is only able to be set by using launchpadlib or the email interface.
    * Like Invalid bugs, Expired bugs do not show up in default searches.
+ 
   * '''Confirmed''':
    * Another reporter has experienced the same bug, this can come in the form of a duplicate bug or a bug comment
    * {{{Confirmed}}} bugs require confirmation from '''someone other than the original reporter'''
    * This helps ensure that the bug is applicable to Ubuntu in general, and not a problem with the reporter's system, therefore...
    * Please don't confirm your own bugs!
+ 
   * '''Triaged''':
    * A member of [[UbuntuBugControl]] believes that the report describes a genuine bug in enough detail that a developer could start working on a fix. ''(also see tip below)''
    * Use this when you are confident that it should be looked at by a developer '''and''' has enough information
    * While not a requirement a bug's Ubuntu task status will be Triaged before any upstream forwarding occurs
    * With bugs about '''linux''' Triaged means that the bug has been tested with the upstream mainline kernel
    * For process bugs (e.g. [[FreezeExceptionProcess|FFes]] and [[SyncRequestProcess|syncs]]) triaged means the action has been approved by the relevant developers.
+ 
   * '''In Progress''':
-   * If '''you''' are working on fixing a bug, set it to {{{In Progress}}} so people know what's going on
+   * If '''you''' are working on fixing a bug '''right now''', set it to {{{In Progress}}} so people know what's going on
-   * {{{In Progress}}} bugs should be assigned to the person working on them 
+   * {{{In Progress}}} bugs should be assigned to the person working on them
+ 
   * '''Fix Committed''':
    * Ubuntu bug task: the changes are pending and to be uploaded soon (it's what PENDINGUPLOAD was in Bugzilla)
     * {{{Fix Committed}}} is also used when an updated package exists in a -proposed repository i.e. hardy-proposed
     * {{{Fix Committed}}} is '''not''' to be used when a patch is attached to a bug
    * Upstream bug task: the fix is in CVS/SVN/bzr or committed to some place
+ 
   * '''Fix Released''':
    * Ubuntu bug task: a fix was uploaded to an official Ubuntu repository
     * N.B. This '''does not''' include -proposed i.e. hardy-proposed
     * Please don't hesitate to add a changelog as a comment, so people know in which package version a bug was fixed
     * If a bug is fixed in the current development release, it is {{{Fix Released}}}. If the bug also [[StableReleaseUpdates | needs to be fixed]] in a stable release, use the "Target to release" link to nominate it for that release.
    * Upstream bug task: a release tarball was announced and is publicly available
+ 
   * '''Won't Fix''':
    * This status is sometimes used when the bug fix is too controversial
    * It is most often used for bugs with a release target that will not be fixed in that particular release but may be fixed later
@@ -65, +76 @@

    * moving to Triaged, or WONTFIX
    * moving ''from'' WONTFIX
    * targeting to a specific Ubuntu release
-  
+ 
+ 
  === Frequently Asked Questions ===
  
  ''If you have a question, please feel free to ask it by emailing the  [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad|BugSquad mailing list]] with your question.''
@@ -83, +95 @@

    * What is the appropiate bug status for issues caused by faulty hardware?
     * The appropriate bug status for such issues is "Invalid".
  
+ 
  ||<tablestyle="width:90%;" style="width: 35px; border: none; -moz-border-radius-topleft: 15px ;-moz-border-radius-bottomleft: 15px; background-color: #F1F1DD; border: none; -moz-border-radius-topright: 15px;-moz-border-radius-bottomright: 15px; font-size: 1em; text-align: center;">{{attachment:IconHelp2.png}}Not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member? If you notice a bug having sufficient information and has not yet been set to Triaged, you'll have to ask someone who is to set the bug to ''Triaged'' for you. Paste the bug number in {{{#ubuntu-bugs}}} channel at [[https://wiki.ubuntu.com/FreeNode|FreeNode]] and say you think the bug should be set to 'Triaged' with importance 'Wishlist / Low / Medium / High / Critical' according to [[Bugs/Importance]]. Someone will notice your comment and set it for you, although not necessarily immediately.||
+ 
  
  ----
  CategoryBugSquad