Re: [Epiphany] Web site

[Christian Rose <menthos menthos com>]

fre 2003-02-14 klockan 13.48 skrev Marco Pesenti Gritti:
> I think we could have something like:
> 
> - Development
> Reporting bugs

I provided the bug reporting page for Galeon, so here is a newer
variant. Attached is also a page about translations.


Christian

Title: $PACKAGE Bug Reporting

$PACKAGE Bug Reporting

Entering a new bug report

$PACKAGE uses the GNOME bug tracking system, GNOME Bugzilla. You can enter a new bug report for $PACKAGE by using the following link:
Enter a new $PACKAGE bug report.

In order to add bugs in Bugzilla, you need an account. You can get one easily by just following the simple instructions on the following link:
Get a new GNOME Bugzilla account.

General instructions on how to write a good and useful bug report are available on the following page:
How to write a useful bug report.

Please only add a new bug report if you are sure that the problem hasn't been reported in Bugzilla before. You can query Bugzilla for already reported $PACKAGE bugs by using the following link and filling in query parameters. Then you just need to click on "Submit query" at the bottom. If you find a bug report that matches your problem, you are welcome to add details about your problem and relevant information about your system and setup as a comment to it. Information about different systems that trigger a certain bug may be a help for developers in finding out why it occurs, and help in producing a fix for the problem.
Search in the list of already reported $PACKAGE bugs.
If you find this interface too complex and only want to search for information in the Summary and Description fields, you can do that directly from here:

Information in the Summary field:
Information in the Description field:

Thanks for reporting your problems and suggestions in Bugzilla. This really helps the developers to keep track of them and organize their work.

Lists with existing bug reports

If you wish to help with the development of $PACKAGE, a good start is to look at the $PACKAGE bugs in Bugzilla that are both currently not resolved, i.e. where there is no fix, and where noone is working on a fix yet. These bugs should be marked UNCONFIRMED/NEW/NEEDINFO/REOPENED (you can find explanations of what exactly these resolutions mean here). Getting this list is easily done as a query in Bugzilla, but here is a shortcut link for your convenience:
List of unresolved $PACKAGE bugs.

To see the bugs where a fix is being worked on, you should search for bugs marked ASSIGNED. Here is a shortcut link for that search:
List of $PACKAGE bugs currently being worked on.

To see all previously reported $PACKAGE bugs, use this link:
List of all reported $PACKAGE bugs.