Software Bug Recording (ie in RISC OS)
7 posts, 3 voices
Andrew Hodgkinson (6)
465 posts
|
This topic has been imported from the old forum. Due to its use of fixed format text, you may need to make your browser view wider in order to see posts with the correct layout. |
Martin Avison (27)
1494 posts
|
The existing Bugs database seems have categories only for problems associated with this website, unless I have misunderstood it (which is quite possible!) Where should bugs be raised which affect any of the RISC OS core, modules, boot or supplied applications? I also suspect there must be a number of currently known bugs ... where are they held? It would seem sensible (if not necessary) to have a single, central, and available list of all known RO bugs, so everyone can see all bugs for a particular module or application, with any workarounds or progress on a fix. This would help anyone doing development work in a particular area - undocumented bugs rarely get fixed! |
Steve Revill (20)
1361 posts
|
Martin Avison (27) wrote: > The existing Bugs database seems have categories only for problems > associated with this website, unless I have misunderstood it (which is > quite possible!) > > Where should bugs be raised which affect any of the RISC OS core, > modules, boot or supplied applications? If the component you want to raise a bug against isn't in the faults database (and most aren't at the moment), send an email to webmaster@riscosopen.org to request for it to be added. > I also suspect there must be a number of currently known bugs ... where > are they held? I'm not aware of there being a definitive list anywhere. Maybe Castle have one but I'm not sure that they do. > It would seem sensible (if not necessary) to have a single, central, and > available list of all known RO bugs, so everyone can see all bugs for a > particular module or application, with any workarounds or progress on a > fix. This would help anyone doing development work in a particular area > - undocumented bugs rarely get fixed! That's the aim of the bug tracker on our site. Hopefully, people will be able to raise all of the faults that they are aware of and that will get the attention of all the developers out there (and someone might actually try to fix a few!) |
|
Martin Avison (27)
1494 posts
|
Steve Revill (20) wrote: > Martin Avison (27) wrote: >> The existing Bugs database seems have categories only for problems >> associated with this website, unless I have misunderstood it (which is >> quite possible!) >> >> Where should bugs be raised which affect any of the RISC OS core, >> modules, boot or supplied applications? > > If the component you want to raise a bug against isn't in the faults > database (and most aren't at the moment), send an email to > webmaster@riscosopen.org to request for it to be added. That sounds rather cumbersome! Perhaps it would be easier if people could raise Bugs under some 'general' category, and 'webmaster' then created a new category and moved the bug into it? I assume when you say 'component' you mean what is listed under 'Part' in the listings? This list could get rather long, I suspect! >> I also suspect there must be a number of currently known bugs ... where >> are they held? > > I'm not aware of there being a definitive list anywhere. Maybe Castle > have one but I'm not sure that they do. That is a REAL shame if there really is no record of any outstanding bugs, and, to be honest, would suprise (and even horrify) me. >> It would seem sensible (if not necessary) to have a single, central, and >> available list of all known RO bugs, so everyone can see all bugs for a >> particular module or application, with any workarounds or progress on a >> fix. This would help anyone doing development work in a particular area >> - undocumented bugs rarely get fixed! > > That's the aim of the bug tracker on our site. Hopefully, people will be > able to raise all of the faults that they are aware of and that will get > the attention of all the developers out there (and someone might > actually try to fix a few!) Yes, as I said, undocumented bugs are unlikely to be fixed! Following on from this, I think the Bugs page badly needs some Help information for it - apart from adding what it should contain, and how to raise a bug for an unlisted component, I really have not managed to work out how the Filtering system works. Is a click over a name different to a click over a [+] ? The bugs listed seem to be the one with a [-] against it, and the ones with [+] are not. Which seems confusing. To me at least! So, some Help would be very useful. I have worked with many bug-tracking systems, and I admit I have not got my head round how (if?) this one will really work yet. |
|
Andrew Hodgkinson (6)
465 posts
|
Martin Avison (27) wrote: > That sounds rather cumbersome! Perhaps it would be easier if people > could raise Bugs under some 'general' category [...] Don't panic. I haven't got around to creating categories for RISC OS related bugs just yet because there aren't any RISC OS sources up there. I didn't expect people to start raising bugs this early - and it's great that they are. So, at some point in the near future, I'll try to get around to adding categories. If you want to get more involved in helping to maintain the bug tracking system, please e-mail the Webmaster address Steve mentions above for more details. |
|
Andrew Hodgkinson (6)
465 posts
|
Martin Avison (27) wrote: > Following on from this, I think the Bugs page badly needs some Help > information for it [...] Although not yet linked to from anywhere else in the site, I've started adding help pages in the Wiki. The index page is here: https://www.riscosopen.org/wiki/documentation/pages/Web+site+help |
|
Martin Avison (27)
1494 posts
|
Andrew Hodgkinson (6) wrote: > Martin Avison (27) wrote: > >> Following on from this, I think the Bugs page badly needs some Help >> information for it [...] > > Although not yet linked to from anywhere else in the site, I've started > adding help pages in the Wiki. The index page is here: > > https://www.riscosopen.org/wiki/documentation/pages/Web+site+help That certainly explains my confusion over the Bugs filter settings: thanks Andrew. |
