[gimp-help] Remove / replace Bugzilla specific information as GIMP has moved to Gitlab
- From: Michael Schumacher <schumaml src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gimp-help] Remove / replace Bugzilla specific information as GIMP has moved to Gitlab
- Date: Sat, 14 Sep 2019 22:39:07 +0000 (UTC)
commit eddf8b0a166af93d0787a7900fbfa5414dc40276
Author: Andre Klapper <ak-47 gmx net>
Date: Sat Sep 14 22:38:57 2019 +0000
Remove / replace Bugzilla specific information as GIMP has moved to Gitlab
Fixes #103
images/C/misc/bugzilla/advanced-search.png | Bin 29694 -> 0 bytes
images/C/misc/bugzilla/enter-bug.png | Bin 25746 -> 0 bytes
images/C/misc/bugzilla/find-specific-bug.png | Bin 16192 -> 0 bytes
src/appendix/bibliography.xml | 18 --
src/appendix/bugs.xml | 464 ++-------------------------
5 files changed, 33 insertions(+), 449 deletions(-)
---
diff --git a/src/appendix/bibliography.xml b/src/appendix/bibliography.xml
index 8d0c68e3c..65d7bc15e 100644
--- a/src/appendix/bibliography.xml
+++ b/src/appendix/bibliography.xml
@@ -225,24 +225,6 @@
</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>
- <releaseinfo>
- <ulink url="http://bugzilla.gnome.org/browse.cgi?product=GIMP";>
- http://bugzilla.gnome.org/browse.cgi?product=GIMP
- </ulink>
- </releaseinfo>
- </biblioentry>
<biblioentry id="bibliography-online-cairo">
<abbrev>CAIRO</abbrev>
<title>Cairo</title>
diff --git a/src/appendix/bugs.xml b/src/appendix/bugs.xml
index 3517ec332..90b0205fe 100644
--- a/src/appendix/bugs.xml
+++ b/src/appendix/bugs.xml
@@ -40,20 +40,17 @@
<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.
+ missing feature—is the same as the procedure for reporting
+ a bug.
</para>
</tip>
<para>
In common with many other free software projects,
<acronym>GIMP</acronym> uses a bug-reporting mechanism called
- <emphasis>Bugzilla</emphasis>.
+ <emphasis>GitLab</emphasis>.
This is a very powerful web-based system, capable of managing thousands
of bug reports without losing track. In fact, <acronym>GIMP</acronym>
- shares its Bugzilla database with the entire Gnome project. At the time
- this is being written, Gnome Bugzilla contains 148632 bug reports–no, make
- that 148633.
+ shares its GitLab database with the entire Gnome project.
</para>
<sect1 id="gimp-bug-confirm">
@@ -96,169 +93,35 @@
<para>
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
- (<ulink url="http://bugzilla.gnome.org/query.cgi"/>),
+ <acronym>GIMP</acronym>'s list of issues
+ (<ulink url="https://gitlab.gnome.org/GNOME/gimp/issues/"/>),
and try to see whether somebody else has already reported the same
thing.
</para>
- <para>
- There are two forms you can use for searching bugs: a simple form to
- <quote>Find a Specific Bug</quote>, and an <quote>Advanced
- Search</quote>.
- </para>
<simplesect id="bugzilla-find-specific-bug">
<title>Find a Specific Bug</title>
- <figure>
- <title>Bugzilla: Find a Specific Bug</title>
- <mediaobject>
- <imageobject>
- <imagedata format="PNG"
- fileref="images/misc/bugzilla/find-specific-bug.png"/>
- </imageobject>
- <caption>
- <para>Searching for bugs using the simple bug search form</para>
- </caption>
- </mediaobject>
- </figure>
<para>
- Using this form, you first should select the
- <guilabel>Product</guilabel> <quote>GIMP</quote> (classified as
- <quote>Other</quote>) using the drop down list. Then you just have to
- enter some (space separated) search terms, e.g.
+ Enter some (space separated) search terms, e.g.
<blockquote>
<para>
<userinput>filter crash</userinput>
</para>
</blockquote>
- in the text box and click on <guibutton>Search</guibutton>.
- </para>
- </simplesect>
-
- <simplesect id="bugzilla-advanced-search">
- <title>The Advanced 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: Advanced Search</title>
- <mediaobject>
- <imageobject>
- <imagedata format="PNG"
- fileref="images/misc/bugzilla/advanced-search.png"/>
- </imageobject>
- <caption>
- <para>
- Searching for bugs using the advanced 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:
+ in the "Search or filter results..." text box and press Enter. By
+ default you only see open reports; you can change this by clicking "All"
+ above the search field.
</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
+ The result is either a list of bug reports – hopefully not too
+ long – or a message saying <quote>Sorry, your filter produced no
+ results</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.
+ you file a bug report and it ends up being closed as a
+ duplicate, don't be too upset: it has happened
+ repeatedly to the author of this documentation.
</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>
@@ -267,120 +130,42 @@
<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 on the Bugzilla page.
+ report on the GitLab page.
</para>
<note>
<para>
The first time you file a bug report, you will be asked to create a
- Bugzilla account. The process is easy and painless, and you probably
+ GitLab account. The process is easy and painless, and you probably
won't even get any spam as a result.
</para>
</note>
<procedure>
<step>
- <title>Bugzilla: Select Classification</title>
+ <title>File a New Issue</title>
<para>
- Go to <ulink url="http://bugzilla.gnome.org/enter_bug.cgi"/>, and
- select the classification <quote>Other</quote>.
+ Go to <ulink url="https://gitlab.gnome.org/GNOME/gimp/issues"/>, and
+ select <guibutton>New issue</guibutton>.
</para>
<!-- IMHO a screenshot is not useful here (ude 2009-08-25) -->
<para>
If you are not logged in, you are automatically redirected to the
login page. After entering your user name (login) and password,
- you get back to the <quote>Select Classification</quote> page.
- </para>
- </step>
-
- <step>
- <title>Bugzilla: Pick Product</title>
- <para>
- Scroll down the next page until you can select the product
- <quote>GIMP</quote>.
+ you get back to the <quote>New Issue</quote> page.
</para>
- <!-- IMHO a screenshot is not useful here (ude 2009-08-25) -->
- <tip>
- <para>
- You can skip the above steps and go directly to
- <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=GIMP"/>
- (You still have to login, of course.)
- </para>
- </tip>
</step>
<step>
- <title>Bugzilla: Enter Bug: <acronym>GIMP</acronym></title>
+ <title>Fill out the Template</title>
<para>
- Selecting <quote>GIMP</quote> as product takes you to the
- following bug report form, which you should fill out as follows.
+ Select <guimenu>Choose a template</guimenu> and choose whether you
+ plan to report a bug or to request a feature.
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>
- <screenshot>
- <screeninfo>2009-08-25</screeninfo>
- <mediaobject>
- <imageobject>
- <imagedata format="PNG"
- fileref="images/misc/bugzilla/enter-bug.png"/>
- </imageobject>
- <caption>
- <para>Enter Bug: <acronym>GIMP</acronym></para>
- </caption>
- </mediaobject>
- </screenshot>
<variablelist>
<varlistentry>
- <term>Component</term>
- <listitem>
- <para>
- Set this to the part of <acronym>GIMP</acronym> that the bug
- affects. Note that you get a short
- <quote>Component Description</quote> in the text box next
- to the list when you select a component.
- </para>
- <para>
- 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>Version</term>
- <listitem>
- <para>
- Set this to the version of <acronym>GIMP</acronym> that you
- are using. You always find the version in the menu of the
- image window:
- <menuchoice>
- <guimenu>Help</guimenu>
- <guimenuitem>About</guimenuitem>
- </menuchoice>.
- </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>OS (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</term>
+ <term>Title</term>
<listitem>
<para>
Give a one-sentence summary that is descriptive enough so that
@@ -393,7 +178,8 @@
<term>Description</term>
<listitem>
<para>
- Describe the problem. Be as specific as you can, and include
+ Describe the problem. Be as specific as you can, try to provide
+ all the information requested from you, 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
@@ -402,15 +188,10 @@
</listitem>
</varlistentry>
</variablelist>
- <para>
- There are more fields which are hidden by default. (Click
- <quote>Show Advanced Fields</quote> to show them.) You can ignore
- them, so we won't describe these fields here.
- </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, click
- on the button <guibutton>Add an attachment</guibutton>,
+ on the button <guibutton>Attach a file</guibutton>,
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
@@ -419,22 +200,19 @@
</para>
<para>
When you have filled out all of these things, press the
- <guibutton>Commit</guibutton> button and your bug report will be
+ <guibutton>Submit issue</guibutton> 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"/>, entering the bug number in
- one of the entry boxes and pressing the
- <guibutton>Find</guibutton> or <guibutton>Quick Search</guibutton>
- button.
+ <ulink url="https://gitlab.gnome.org/GNOME/gimp/issues/"/>.
</para>
</step>
</procedure>
</sect1>
- <sect1 id="gimp-bug-submitted">
+<!-- <sect1 id="gimp-bug-submitted">
<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
@@ -442,182 +220,6 @@
that describes how it is currently being handled. Here are the
possible values of <emphasis>Status</emphasis> and what they mean:
</para>
- <variablelist>
- <varlistentry>
- <term>Unconfirmed</term>
- <listitem>
- <para>
- This is the initial status of a bug report, from the time it is
- submitted until one of the maintainers reads it and decides
- whether it is really a valid bug report. Sometimes the maintainers
- aren't sure, and in the meantime leave the status as
- <quote>Unconfirmed</quote>. In the worst cases, a bug report can
- stay
- unconfirmed for a year or longer, but this is considered a bad
- thing and does not happen very often.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>New</term>
- <listitem>
- <para>
- This means that the bug report has been read by one of the
- maintainers, and is considered, for the moment at least, to be
- valid. It does not necessarily mean that anything is going to be
- done about it immediately: some bug reports, especially
- enhancement requests, may be perfectly valid and still go for a
- long time before anybody is able to deal with them. Many bugs, on
- the other hand, are fixed within hours of being reported.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Assigned</term>
- <listitem>
- <para>
- This means that a specific person has agreed to work on the bug.
- It does not, this world being the kind of world that it is, mean
- that that person will actually <emphasis>do</emphasis>
- anything in particular, so for practical purposes this status
- means nearly the same thing as <quote>New</quote>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Reopened</term>
- <listitem>
- <para>
- This means that the bug report was at some point considered by the
- maintainers to be resolved (i.e., finished), but new information
- came in that caused them to change their minds: most likely, a
- change that was intended to fix the problem did not completely
- work.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Needinfo</term>
- <listitem>
- <para>
- This is a status you should pay particular attention to. It means
- that you did not supply enough information in your bug report to
- enable anything to be done about it. In most cases, no further
- action will be taken on the bug report until you supply additional
- information (by adding a comment). If too much time goes by
- without any input from you, the bug report will eventually be
- resolved as <quote>Incomplete</quote>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Resolved</term>
- <listitem>
- <para>
- This means that the maintainers believe that they have finished
- dealing with the bug report. If you disagree, you can re-open it,
- but since you cannot force anybody to work on a bug against their
- will, you should have a good reason for doing so. Bugs can be
- resolved in a variety of ways. Here are the possible values of
- <emphasis>Resolution</emphasis> and what they mean:
- </para>
- <variablelist>
- <varlistentry>
- <term>Fixed</term>
- <listitem>
- <para>
- The bug report is considered valid, and
- <acronym>GIMP</acronym> has been
- changed in a way that is considered to fix it.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Wontfix</term>
- <listitem>
- <para>
- The maintainers agree that the bug report is valid, but it
- would take so much effort to fix, in relation to its
- importance, that it is not worth the trouble.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Duplicate</term>
- <listitem>
- <para>
- This means that the same bug has already been reported by
- somebody else. If you see this resolution, you will also see
- a pointer to the earlier bug report, which will often give
- you a lot of useful information.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Notabug</term>
- <listitem>
- <para>
- This means that the behavior described in the bug
- report is intentional. It may seem like a bug to you
- (and there may be many people who agree with you), but
- the program is working the way it was intended to
- work, and the developers don't want to change it.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>NotGnome</term>
- <listitem>
- <para>
- The bug report is valid, but it can't be addressed by
- changing <acronym>GIMP</acronym>. Problems in operating
- systems, window managers, or libraries that
- <acronym>GIMP</acronym> depends on will often be
- given this resolution. Sometimes the next appropriate step
- is to file a bug report for the software that is really at
- fault.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Incomplete</term>
- <listitem>
- <para>
- The bug report did not contain enough information for
- anything to be done about it, and the reporter did not
- respond to requests for more information. Usually a bug
- report will be open for at least a month or two before it is
- resolved in this way.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Invalid</term>
- <listitem>
- <para>
- Something is wrong with the form of the bug report: most
- commonly, the reporter has accidentally submitted the same
- bug report multiple times. (This can easily happen by
- mistake with some web browsers.) Bug reports that
- incorrectly describe how the program behaves may also be
- resolved as Invalid.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <note>
- <para>
- If you disagree with the resolution of a bug report, you are
- always free to add your comments to it. Any comment added to any
- bug report, resolved or not, causes email to be sent to the
- <acronym>GIMP</acronym>
- Bugzilla mailing list, so it will at least be seen by the
- maintainers. This does not, of course, mean that they will
- necessarily respond to it.
- </para>
- </note>
- </listitem>
- </varlistentry>
- </variablelist>
</sect1>
+-->
</appendix>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
