julipedia.blogspot.com/2004/06/dealing-with-bug-reports.html

Preview meta tags from the julipedia.blogspot.com website.

Linked Hostnames

9

Thumbnail

Search Engine Appearance

Google

https://julipedia.blogspot.com/2004/06/dealing-with-bug-reports.html

Dealing with bug reports - Julio Merino (jmmv.dev)

Some days ago I posted a message, titled "The art of bug reporting", which gave some tips to fill good bug reports. Today, I'm going to review this same process from the developer's point of view, who has to handle these reports. Developers are often organized in workgroups; this way new bug reports can be easily assigned to one of these groups. This classification is done automatically, based on what the submitter specified in the respective field. Even though they can be reclassified (in case of bogus choices) by a team specially designed to review bugs (or individual developers). For example, GNOME has the Bugsquad team (which you can start to help now!), while NetBSD has no such workgroup (yet).



Bing

Dealing with bug reports - Julio Merino (jmmv.dev)

https://julipedia.blogspot.com/2004/06/dealing-with-bug-reports.html

Some days ago I posted a message, titled "The art of bug reporting", which gave some tips to fill good bug reports. Today, I'm going to review this same process from the developer's point of view, who has to handle these reports. Developers are often organized in workgroups; this way new bug reports can be easily assigned to one of these groups. This classification is done automatically, based on what the submitter specified in the respective field. Even though they can be reclassified (in case of bogus choices) by a team specially designed to review bugs (or individual developers). For example, GNOME has the Bugsquad team (which you can start to help now!), while NetBSD has no such workgroup (yet).



DuckDuckGo

https://julipedia.blogspot.com/2004/06/dealing-with-bug-reports.html

Dealing with bug reports - Julio Merino (jmmv.dev)

Some days ago I posted a message, titled "The art of bug reporting", which gave some tips to fill good bug reports. Today, I'm going to review this same process from the developer's point of view, who has to handle these reports. Developers are often organized in workgroups; this way new bug reports can be easily assigned to one of these groups. This classification is done automatically, based on what the submitter specified in the respective field. Even though they can be reclassified (in case of bogus choices) by a team specially designed to review bugs (or individual developers). For example, GNOME has the Bugsquad team (which you can start to help now!), while NetBSD has no such workgroup (yet).

  • General Meta Tags

    13
    • title
      Dealing with bug reports - Julio Merino (jmmv.dev)
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width,initial-scale=1,shrink-to-fit=no
    • twitter:site
      @jmmv
  • Open Graph Meta Tags

    6
    • og:site_name
      Julio Merino (jmmv.dev)
    • og:title
      Dealing with bug reports - Julio Merino (jmmv.dev)
    • og:description
      Some days ago I posted a message, titled "The art of bug reporting", which gave some tips to fill good bug reports. Today, I'm going to review this same process from the developer's point of view, who has to handle these reports. Developers are often organized in workgroups; this way new bug reports can be easily assigned to one of these groups. This classification is done automatically, based on what the submitter specified in the respective field. Even though they can be reclassified (in case of bogus choices) by a team specially designed to review bugs (or individual developers). For example, GNOME has the Bugsquad team (which you can start to help now!), while NetBSD has no such workgroup (yet).
    • og:url
      https://jmmv.dev/2004/06/dealing-with-bug-reports.html
    • og:type
      blog
  • Link Tags

    7
    • alternate
      /feed.xml
    • canonical
      https://jmmv.dev/2004/06/dealing-with-bug-reports.html
    • icon
      /images/favicons/favicon-16x16.png
    • icon
      /images/favicons/favicon-32x32.png
    • icon
      /images/favicons/favicon-96x96.png

Links

32