Bug Reporting: Difference between revisions

From RISC OS
Jump to navigationJump to search
(Put in more links)
(Remove outdated info about reporting via Bugzilla)
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Introduction ==
== Introduction ==


riscos.info accepts bug reports against any program hosted here, or against the site itself. These can includes obvious faults, feature requests, or the simplest of suggested fixes. Making these bugs readily available allows developers to prioritize issues, allow planning, and ensures tracking so that when a problem is fixed, both the reporter and developer know they can move on.
riscos.info accepts bug reports against any program hosted here, or against the site itself. These can include obvious faults, feature requests, or the simplest of suggested fixes. We previously had a Bugzilla instance for holding a bug database, but this became a target of spam. For now please post bug reports to the [http://www.riscos.info/cgi-bin/mailman/listinfo/gcc GCCSDK mailing list] where many of the developers congregate.

Reporting bugs also removes some burden from developers, as it helps ensure a consistent style and format that is not readily possible for example in email.

This section is still under going work. We hope to have more detailed instructions soon.


== Guidelines ==
== Guidelines ==
Line 15: Line 11:
* [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]
* [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]


== Bug Categories ==
== What is valid to report ==

List of bugs in a specific group:

* [http://www.riscos.info/cgi-bin/bugzilla3/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All bugs] - every bug in the system

* [http://www.riscos.info/cgi-bin/bugzilla3/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=GCC%2FGCCSDK&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= GCC] - bugs against GCC native and cross compiler, UnixLib and shared library support.


Anything related to software hosted on riscos.info. This includes:
* [http://www.riscos.info/cgi-bin/bugzilla3/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Firefox&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Firefox] - RISC OS Mozilla Firefox bug reports and feature requests.


* Regular bugs, and obvious faults in software
* [http://www.riscos.info/cgi-bin/bugzilla3/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Ports&component=Games&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Games] - Any bugs or against riscos.info game ports, including suggestions for new game ports.
* Feature requests in existing software
* Updates of existing riscos.info ports
* Updates of ports elsewhere, where the developer might not have any further interest
* Requests for new ports


The last is of particular note - it allows us to track all the related problems that immediately prevent porting of a given piece of software.
* [http://www.riscos.info/cgi-bin/bugzilla3/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Ports&component=Other&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Other ports] - Any bugs against any non-game ports, including libraries, command line utilities, the GCCSDK Autobuilder and other porting tools.


== New Bugs ==
== How to report a bug ==


Where relevant, please include:
To enter a new bug, or for a more specific search:


* Version of RISC OS
* [http://www.riscos.info/cgi-bin/bugzilla3/index.cgi Bugzilla interface]
* Repeatable steps
* Where to get the source, if it's a port/update request
* Any valid URLs, mailing list/usenet related information.

Latest revision as of 08:45, 24 June 2023

Introduction

riscos.info accepts bug reports against any program hosted here, or against the site itself. These can include obvious faults, feature requests, or the simplest of suggested fixes. We previously had a Bugzilla instance for holding a bug database, but this became a target of spam. For now please post bug reports to the GCCSDK mailing list where many of the developers congregate.

Guidelines

Bug reporting needs to follow certain guidelines to be useful to developers. It needs to have comprehensive details, and ideally be repeatable. The following guide is required reading before submitting any bugs to riscos.info:

What is valid to report

Anything related to software hosted on riscos.info. This includes:

  • Regular bugs, and obvious faults in software
  • Feature requests in existing software
  • Updates of existing riscos.info ports
  • Updates of ports elsewhere, where the developer might not have any further interest
  • Requests for new ports

The last is of particular note - it allows us to track all the related problems that immediately prevent porting of a given piece of software.

How to report a bug

Where relevant, please include:

  • Version of RISC OS
  • Repeatable steps
  • Where to get the source, if it's a port/update request
  • Any valid URLs, mailing list/usenet related information.
Retrieved from "http://www.riscos.info/index.php?title=Bug_Reporting&oldid=6323"