[gimp-help-2: 1/2] Update Bugzilla description
- From: Ulf-D. Ehlert <ulfehlert src gnome org>
- To: svn-commits-list gnome org
- Subject: [gimp-help-2: 1/2] Update Bugzilla description
- Date: Thu, 25 Jun 2009 18:34:24 +0000 (UTC)
commit 1a8dcc04119101a4ca80ec922c744c7c90108bcd
Author: Ulf-D. Ehlert <ulfehlert svn gnome org>
Date: Thu Jun 25 20:20:40 2009 +0200
Update Bugzilla description
images/C/misc/bugzilla/enter-bug-info.png | Bin 0 -> 6251 bytes
images/C/misc/bugzilla/enter-bug.png | Bin 0 -> 37958 bytes
images/C/misc/bugzilla/pick-product.png | Bin 0 -> 25037 bytes
images/C/misc/bugzilla/query-complicated.png | Bin 0 -> 45476 bytes
images/C/misc/bugzilla/query-short.png | Bin 0 -> 7045 bytes
images/C/misc/bugzilla/simple-bug-guide.png | Bin 0 -> 23478 bytes
images/C/using/bugzilla-page.png | Bin 23067 -> 0 bytes
src/appendix/bibliography.xml | 9 +
src/appendix/bugs.xml | 656 +++++++++++++++++---------
9 files changed, 451 insertions(+), 214 deletions(-)
---
diff --git a/images/C/misc/bugzilla/enter-bug-info.png b/images/C/misc/bugzilla/enter-bug-info.png
new file mode 100644
index 0000000..beff140
Binary files /dev/null and b/images/C/misc/bugzilla/enter-bug-info.png differ
diff --git a/images/C/misc/bugzilla/enter-bug.png b/images/C/misc/bugzilla/enter-bug.png
new file mode 100644
index 0000000..d1c6d97
Binary files /dev/null and b/images/C/misc/bugzilla/enter-bug.png differ
diff --git a/images/C/misc/bugzilla/pick-product.png b/images/C/misc/bugzilla/pick-product.png
new file mode 100644
index 0000000..82f5e68
Binary files /dev/null and b/images/C/misc/bugzilla/pick-product.png differ
diff --git a/images/C/misc/bugzilla/query-complicated.png b/images/C/misc/bugzilla/query-complicated.png
new file mode 100644
index 0000000..059b1e6
Binary files /dev/null and b/images/C/misc/bugzilla/query-complicated.png differ
diff --git a/images/C/misc/bugzilla/query-short.png b/images/C/misc/bugzilla/query-short.png
new file mode 100644
index 0000000..c993c9d
Binary files /dev/null and b/images/C/misc/bugzilla/query-short.png differ
diff --git a/images/C/misc/bugzilla/simple-bug-guide.png b/images/C/misc/bugzilla/simple-bug-guide.png
new file mode 100644
index 0000000..9874a49
Binary files /dev/null and b/images/C/misc/bugzilla/simple-bug-guide.png differ
diff --git a/src/appendix/bibliography.xml b/src/appendix/bibliography.xml
index d8da21d..285d28c 100644
--- a/src/appendix/bibliography.xml
+++ b/src/appendix/bibliography.xml
@@ -206,6 +206,15 @@
</ulink>
</releaseinfo>
</biblioentry>
+ <biblioentry id="bibliography-online-bugzilla">
+ <abbrev>BUGZILLA</abbrev>
+ <title>Bugzilla</title>
+ <releaseinfo>
+ <ulink url="http://bugzilla.gnome.org";>
+ http://bugzilla.gnome.org
+ </ulink>
+ </releaseinfo>
+ </biblioentry>
<biblioentry id="bibliography-online-bugzilla-gimp">
<abbrev>BUGZILLA-GIMP</abbrev>
<title>Bugzilla-GIMP</title>
diff --git a/src/appendix/bugs.xml b/src/appendix/bugs.xml
index 930b51e..974e0be 100644
--- a/src/appendix/bugs.xml
+++ b/src/appendix/bugs.xml
@@ -1,14 +1,15 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.docbook.org/xml/4.3/docbookx.dtd";>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+ "http://www.docbook.org/xml/4.3/docbookx.dtd";>
<!-- section history:
+ 2009-06-25 ude: updated (incl. new screenshots)
2006-10-21 lexa: added german translation
2006-02-27 no added by kolbjoern stuestoel
2005-12-12 moved to the appendix and made it valid docbook by lexa
-->
<appendix id="gimp-introduction-bugs">
- <title>
- <phrase>Reporting Bugs and Requesting Enhancements</phrase>
- </title>
+ <title>Reporting Bugs and Requesting Enhancements</title>
+
<indexterm>
<primary>GIMP</primary>
<secondary>Bugs</secondary>
@@ -16,6 +17,7 @@
<indexterm>
<primary>Bugs</primary>
</indexterm>
+
<para>
Sad to say, no version of <acronym>GIMP</acronym>
has yet been absolutely perfect. Even sadder, it is likely that no version
@@ -36,11 +38,10 @@
<tip>
<para>
The procedure for making an <emphasis>enhancement
- request</emphasis>â??that is, for asking the developers to add a
- missing featureâ??is nearly the same as the procedure for
- reporting a bug. The only thing you do differently is to mark the
- report as an <quote>enhancement</quote> at the appropriate stage, as
- described below.
+ request</emphasis>—that is, for asking the developers to add a
+ missing feature—is nearly the same as the procedure for reporting
+ a bug. The only thing you do differently is to mark the report as an
+ <quote>enhancement</quote> at the appropriate stage, as described below.
</para>
</tip>
<para>
@@ -53,10 +54,9 @@
this is being written, Gnome Bugzilla contains 148632 bug reportsâ??no, make
that 148633.
</para>
+
<sect1>
- <title>
- <phrase>Making sure it's a Bug</phrase>
- </title>
+ <title>Making sure it's a Bug</title>
<para>
The first thing you should do, before reporting a bug, is to make
an effort to verify that what you are seeing really
@@ -76,11 +76,10 @@
<note>
<para>
Actually there are a few things that are known to cause
- <acronym>GIMP</acronym> to
- crash but have turned out to be too inconvenient to be worth
- fixing. One of them is asking <acronym>GIMP</acronym> to do
- something that requires vast amounts of memory, such as creating an
- image one million pixels on a side.
+ <acronym>GIMP</acronym> to crash but have turned out to be too
+ inconvenient to be worth fixing. One of them is asking
+ <acronym>GIMP</acronym> to do something that requires vast amounts of
+ memory, such as creating an image one million pixels on a side.
</para>
</note>
<para>
@@ -97,106 +96,189 @@
If after due consideration you still think you have a legitimate
bug report or enhancement request, the next step is to go to
<acronym>GIMP</acronym>'s bugzilla query page
- (http://bugzilla.gnome.org/query.cgi),
+ (<ulink url="http://bugzilla.gnome.org/query.cgi"/>),
and try to see whether somebody else has already reported the same
- thing. The query page allows you to search the bug database in a
- variety of ways. Unfortunately this page is a bit more
- complicated to use than it really ought to be, but here is
- basically what you should do:
+ thing.
</para>
- <figure>
- <title>
- <phrase>Bugzilla page</phrase>
- </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/using/bugzilla-page.png" format="PNG"/>
- </imageobject>
- </mediaobject>
- </figure>
<para>
- In this page, some items are hyperlinks leading to detailed help.
+ There are two forms you can use for searching bugs: a simple
+ <quote>short</quote> form, and an advanced <quote>complicated</quote>
+ form.
</para>
- <variablelist>
- <varlistentry>
- <term>Summary:</term>
- <listitem>
- <para>
- Set this to <quote>contains any of the words/strings</quote>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>(the adjoining entry area)</term>
- <listitem>
- <para>
- Give one or more words that somebody would be likely to use in
- writing a one-sentence summary of a bug similar to yours. For
- example, if the problem is that zooming too much causes
- <acronym>GIMP</acronym> to
- crash, the word <quote>zoom</quote> would be good.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Product:</term>
- <listitem>
- <para>Set this to <quote>GIMP</quote></para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Component:, Version:, Target:</term>
- <listitem>
- <para>Don't do anything for these.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Text information:</term>
- <listitem>
+
+ <simplesect id="bugzilla-query-short">
+ <title>The Short Bug Search Form</title>
+ <figure>
+ <title>Bugzilla: Short Bug Search Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata format="PNG"
+ fileref="images/misc/bugzilla/query-short.png"/>
+ </imageobject>
+ <caption>
+ <para>Searching for bugs using the short bug search form</para>
+ </caption>
+ </mediaobject>
+ </figure>
+ <para>
+ Using the short form, you just have to enter some (space separated)
+ search terms, e.g.
+ <blockquote>
<para>
- For now, leave this alone. If your search does not turn up
- anything, it might be worth entering your search terms in the
- <quote>comment</quote> area here, but this often turns out to
- give you either great masses of stuff or nothing.
+ <userinput>gimp filter crash</userinput>
</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Status:</term>
- <listitem>
+ </blockquote>
+ in the text box and click on <guilabel>Search</guilabel>. Even
+ elaborate terms like
+ <blockquote>
<para>
- This field encodes the status of a bug report: whether it is still
- open, has been resolved, etc. You want to see all relevant bug
- reports, regardless of status, so you should hold down the mouse
- and sweep it across all entries. Leaving it alone will not work.
+ <userinput>product:gimp severity>=major</userinput>
</para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- When you have set these things up, click on the <quote>Search</quote>
- button at
- either the top or bottom; they both do the same thing. The result is
- either a list of bug reportsâ??hopefully not too longâ??or a message saying
- <quote>Zarro boogs found</quote>. If you don't find a related bug
- report by doing
- this, it may be worth trying another search with different terms. If in
- spite of your best efforts, you file a bug report and it ends up being
- resolved as <quote>Duplicate</quote>, don't be too upset: it has
- happened repeatedly to the author of this documentation, who works with
- <acronym>GIMP</acronym> Bugzilla nearly every day.
- </para>
+ </blockquote>
+ are possible.
+ </para>
+ <tip>
+ <para>
+ Clicking on <quote>Help</quote> will lead you to an excellent help
+ page, including some instructive <quote>Examples with
+ Explanations</quote>.
+ </para>
+ </tip>
+ </simplesect>
+
+ <simplesect id="bugzilla-query-complicated">
+ <title>The Complicated Bug Search Form</title>
+ <para>
+ The alternative form, the advanced query page, allows you to search
+ the bug database in a variety of ways:
+ </para>
+ <figure>
+ <title>Bugzilla: Complicated Bug Search Form</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata format="PNG"
+ fileref="images/misc/bugzilla/query-complicated.png"/>
+ </imageobject>
+ <caption>
+ <para>
+ Searching for bugs using the complicated bug search form
+ </para>
+ </caption>
+ </mediaobject>
+ </figure>
+ <para>
+ Unfortunately this page is a bit more <quote>complicated</quote> to
+ use than it really ought to be (at least, some items are hyperlinks
+ leading to detailed help), but here is basically what you should do:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Summary</term>
+ <listitem>
+ <para>
+ Set this to <quote>contains any of the words/strings</quote>.
+ </para>
+ <para>
+ In the adjoining text box, give one or more words that somebody
+ would be likely to use in writing a one-sentence summary of a
+ bug similar to yours. For example, if the problem is that
+ zooming too much causes <acronym>GIMP</acronym> to crash, the
+ word <quote>zoom</quote> would be good.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Classification</term>
+ <listitem>
+ <para>
+ Other (since <acronym>GIMP</acronym> is not part of the GNOME
+ Desktop suite).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Product</term>
+ <listitem>
+ <para>
+ Set this to <quote>GIMP</quote> (or <quote>GEGL</quote>,
+ <quote>GIMP-manual</quote> etc., if appropriate).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Component, Version, Target Milestone</term>
+ <listitem>
+ <para>Don't do anything for these.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Comment, Whiteboard, Keywords</term>
+ <listitem>
+ <para>
+ For now, leave this alone. If your search does not turn up
+ anything, it might be worth entering your search terms in the
+ <quote>Comment</quote> area here, but this often turns out to
+ give you either great masses of stuff or nothing.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Status</term>
+ <listitem>
+ <para>
+ This field encodes the status of a bug report: whether it is
+ still open, has been resolved, etc. You want to see all relevant
+ bug reports, regardless of status, so you should hold down the
+ mouse and sweep it across all entries. Leaving it alone will not
+ work.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Resolution, Severity, Priority, OS</term>
+ <listitem>
+ <para>
+ Usually you shouldn't touch these items.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>(Any other items)</term>
+ <listitem>
+ <para>Don't do anything for these.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ When you have set these things up, click on the <quote>Search</quote>
+ button at either the top or bottom; they both do the same thing. The
+ result is either a list of bug reports – hopefully not too long
+ – or a message saying <quote>Zarro boogs found</quote>. If you
+ don't find a related bug report by doing this, it may be worth trying
+ another search with different terms. If in spite of your best efforts,
+ you file a bug report and it ends up being resolved as
+ <quote>Duplicate</quote>, don't be too upset: it has happened
+ repeatedly to the author of this documentation, who works with
+ <acronym>GIMP</acronym> Bugzilla nearly every day.
+ </para>
+ <tip>
+ <para>
+ Depending on your browser configuration (i.e. whether JavaScript is
+ enabled), you may see a link
+ <guilabel>Give me some help</guilabel>. If you click
+ on this link, the page will be reloaded and then moving the mouse
+ pointer over an input widget produces a little help popup.
+ </para>
+ </tip>
+ </simplesect>
</sect1>
+
<sect1>
- <title>
- <phrase>Reporting the Bug</phrase>
- </title>
+ <title>Reporting the Bug</title>
<para>
Okay, so you have done everything you could to make sure, and you still
think it's probably a bug. You should then go ahead and file a bug
- report. To do this, begin by going to
- http://bugzilla.gnome.org/enter_bug.cgi, and go down the page until you
- can select the component <quote>GIMP</quote>.
+ report on the Bugzilla page.
</para>
<note>
<para>
@@ -206,119 +288,265 @@
</para>
</note>
<para>
- This takes you to the bug report form, which you should fill out
- as follows. Note that most of the information you enter can be
- changed later by the developers if you get it wrong, so try to get
- it right but don't be obsessive about it.
- </para>
- <variablelist>
- <varlistentry>
- <term>Summary</term>
- <listitem>
- <para><!--changed 041017-->
- Give a one-sentence summary that is descriptive enough so that
- somebody searching for similar bugs would find your bug report on
- the basis of the words this summary contains.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Steps to reproduce the bug</term>
- <listitem>
- <para>
- Follow the directions. Be as specific as you can, and include all
- information that you think might possibly be relevant. The classic
- totally useless bug report is,
- <quote>GIMP crashes. This program sucks</quote>.
- There is no hope that the developers can solve a problem if they
- can't tell what it is. If at all possible, give a procedure that
- will reliably reproduce the buggy behavior, and give it in enough
- detail so that a moron could follow it.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Component</term>
- <listitem>
- <para>
- Set this to the part of <acronym>GIMP</acronym> that the bug
- affects. You have to pick something here, but if you aren't
- sure, make a guess and don't worry about it.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Severity</term>
- <listitem>
- <para>
- In most cases you should either leave this as
- <quote>Normal</quote> or set it to <quote>Enhancement</quote>,
- if it is an enhancement request rather than a
- malfunction. The maintainers will adjust the severity if they
- think it is warranted.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Priority</term>
- <listitem>
- <para>
- In most cases you should leave this at <quote>Normal</quote>,
- and allow the maintainers to adjust it. Setting the priority to
- <quote>Immediate</quote> or <quote>Urgent</quote> usually just
- manages to annoy people.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Version</term>
- <listitem>
- <para>
- Set this to the version of <acronym>GIMP</acronym> that you are
- using. Leave the Gnome version unspecified.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Operating System</term>
- <listitem>
- <para>
- Set this to your OS unless you have a very good reason for
- thinking that the bug applies to all operating systems.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- You can ignore the rest. When you have filled out all of these things,
- press the <quote>Commit</quote> button and your bug report will be
- submitted. It will
- be assigned a number, which you may want to make note of; you will,
- however, be emailed any time somebody makes a comment on your bug report
- or otherwise alters it, so you will receive reminders in any case. You
- can see the current state of your bug report at any time by going to
- http://bugzilla.gnome.org and, at the bottom of the page, in the
- <quote>Actions:</quote> area, entering the bug number and pressing
- the <quote>Find</quote> button.
- </para>
- <para>
- Sometimes it is very helpful to augment a bug report with a screenshot
- or some other type of data. If you need to do this, go to the web page
- for your bug report, click on the link
- <quote>Create a New Attachment</quote>, and
- follow the directions. But please don't do this unless you think the
- attachment is really going to be usefulâ??and if you need to attach a
- screenshot, don't make it any larger than necessary. Bug reports are
- likely to remain on the system for years, so there is no sense in
- wasting memory.
+ There are two ways to file a bug report: a simple way using a guided
+ tour, or a more advanced way using a single page.
</para>
+
+ <simplesect id="bugzilla-simple-bug-guide">
+ <title>The Simple Bug Guide</title>
+ <para>
+ If you go to
+ <ulink url=" http://bugzilla.gnome.org/simple-bug-guide.cgi"/>,
+ you have to login, of course, and then you start a guided tour
+ with the following dialog:
+ </para>
+ <figure>
+ <title>Bugzilla: Simple Bug Guide</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata format="PNG"
+ fileref="images/misc/bugzilla/simple-bug-guide.png"/>
+ </imageobject>
+ <caption>
+ <para>First dialog window of the simple bug guide</para>
+ </caption>
+ </mediaobject>
+ </figure>
+ <para>
+ First you will have to answer a few questions, that is you just have
+ to select one of several choices. As you can see in the above figure,
+ you will always get some useful explanations.
+ </para>
+ <variablelist>
+ <para>You will be asked for</para>
+ <varlistentry>
+ <term>Bug type</term>
+ <listitem>
+ <para>
+ <quote>Normal</quote> is usually a good choice (but have a look
+ at the explanations).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Classification and Application</term>
+ <listitem>
+ <para>
+ Select Classification <quote>Other</quote>, and Application
+ <quote>GIMP</quote>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Component</term>
+ <listitem>
+ <para>
+ Set this to the part of <acronym>GIMP</acronym> that the bug
+ affects. You have to pick something here, but if you aren't
+ sure, make a guess and don't worry about it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Severity</term>
+ <listitem>
+ <para>
+ In most cases you should either leave this as
+ <quote>Normal</quote> or set it to <quote>Enhancement</quote>,
+ if it is an enhancement request rather than a malfunction. The
+ maintainers will adjust the severity if they think it is
+ warranted.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Version</term>
+ <listitem>
+ <para>
+ Set this to the version of <acronym>GIMP</acronym> that you are
+ using. See
+ <menuchoice>
+ <guimenu>Help</guimenu>
+ <guimenuitem>About</guimenuitem>
+ </menuchoice>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Then you get to the guided bug report form, which you should fill out
+ as follows:
+ </para>
+ <figure>
+ <title>Bugzilla: Enter bug information</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata format="PNG"
+ fileref="images/misc/bugzilla/enter-bug-info.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <variablelist id="bugzilla-bug-information">
+ <varlistentry>
+ <term>Summary</term>
+ <listitem>
+ <para>
+ Give a one-sentence summary that is descriptive enough so that
+ somebody searching for similar bugs would find your bug report on
+ the basis of the words this summary contains.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Description</term>
+ <listitem>
+ <para>
+ Describe the problem. Be as specific as you can, and include all
+ information that you think might possibly be relevant. The
+ classic totally useless bug report is, <quote>GIMP crashes. This
+ program sucks</quote>. There is no hope that the developers can
+ solve a problem if they can't tell what it is.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Steps to reproduce the bug</term>
+ <listitem>
+ <para>
+ If at all possible, give a procedure that will reliably
+ reproduce the buggy behavior, and give it in enough detail so
+ that a moron could follow it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Additional information</term>
+ <listitem>
+ <para>
+ Here you may add any additional information that might be
+ relevant, but it's not necessary to duplicate your previous
+ reports.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </simplesect>
+
+ <simplesect id="bugzilla-advanced-bugreport">
+ <title>The Advanced Bugreport</title>
+ <para>
+ To use the advanced bug form, go to
+ <ulink url="http://bugzilla.gnome.org/enter_bug.cgi"/>,
+ and scroll down the page until you can select the product
+ <quote>GIMP</quote>.
+ </para>
+ <figure>
+ <title>Bugzilla: Enter Bug (pick a product)</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata format="PNG"
+ fileref="images/misc/bugzilla/pick-product.png"/>
+ </imageobject>
+ <caption>
+ <para>Select the product: <acronym>GIMP</acronym></para>
+ </caption>
+ </mediaobject>
+ </figure>
+ <tip>
+ <para>
+ You can skip this step by using
+ <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=GIMP"/>.
+ </para>
+ </tip>
+
+ <para>
+ Selecting <quote>GIMP</quote> as product takes you to the following
+ bug report form, which you should fill out as follows. Note that most
+ of the information you enter can be changed later by the developers if
+ you get it wrong, so try to get it right but don't be obsessive about
+ it.
+ </para>
+ <figure>
+ <title>Bugzilla: Enter Bug (<acronym>GIMP</acronym>)</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata format="PNG"
+ fileref="images/misc/bugzilla/enter-bug.png"/>
+ </imageobject>
+ <caption>
+ <para>The main bugreport page</para>
+ </caption>
+ </mediaobject>
+ </figure>
+ <variablelist>
+ <varlistentry>
+ <term>Version, Severity</term>
+ <listitem>
+ <para>
+ See <link linkend="bugzilla-simple-bug-guide">Simple Bug
+ Guide</link>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Operating System</term>
+ <listitem>
+ <para>
+ Set this to your OS unless you have a very good reason for
+ thinking that the bug applies to all operating systems.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Summary, Description</term>
+ <listitem>
+ <para>
+ See <link linkend="bugzilla-bug-information">Enter bug
+ information</link>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <!--
+ <varlistentry>
+ <term>Priority</term>
+ <listitem>
+ <para>
+ In most cases you should leave this at <quote>Normal</quote>,
+ and allow the maintainers to adjust it. Setting the priority to
+ <quote>Immediate</quote> or <quote>Urgent</quote> usually just
+ manages to annoy people.
+ </para>
+ </listitem>
+ </varlistentry>
+ -->
+ </variablelist>
+ <para>
+ You can ignore the rest. When you have filled out all of these things,
+ press the <guilabel>Commit</guilabel> button and your bug report will
+ be submitted. It will be assigned a number, which you may want to make
+ note of; you will, however, be emailed any time somebody makes a
+ comment on your bug report or otherwise alters it, so you will receive
+ reminders in any case. You can see the current state of your bug
+ report at any time by going to
+ <ulink url="http://bugzilla.gnome.org"/> and, at the
+ bottom of the page, in the <quote>Actions:</quote> area, entering the
+ bug number and pressing the <guilabel>Find</guilabel> button.
+ </para>
+ <para>
+ Sometimes it is very helpful to augment a bug report with a screenshot
+ or some other type of data. If you need to do this, go to the web page
+ for your bug report, click on the link <quote>Create a New
+ Attachment</quote>, and follow the directions. But please don't do
+ this unless you think the attachment is really going to be
+ useful—and if you need to attach a screenshot, don't make it any
+ larger than necessary. Bug reports are likely to remain on the system
+ for years, so there is no sense in wasting memory.
+ </para>
+ </simplesect>
</sect1>
+
<sect1>
- <title>
- <phrase>
- What Happens to a Bug Report after you Submit it
- </phrase>
- </title>
+ <title>What Happens to a Bug Report after you Submit it</title>
<para>
At any time after it is submitted, a bug report has a
<quote>Status</quote>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
