Re: Discussion on bugs.
Could we use Bugzilla?
Bug Tracking
I don't like Bugzilla either. Being a pain to use, it seems like it must get in the way of letting developers know about bugs. Imagine what a beginner to Puppy would think of it. I don't know what developers think of it.
Barry has said he might set up a webpage form for reporting bugs, similar to this page. But then he also said it would be nice if people could view the log of already-submitted bugs. It seems to me that one way to kill both birds with one go is a bug reporting scheme organized like a forum.
I think I would do a better job of reporting a bug and not leave important stuff out if I saw some examples of how to report a bug, to sort of get me thinking along the right lines before I filed my report.
Barry has said he might set up a webpage form for reporting bugs, similar to this page. But then he also said it would be nice if people could view the log of already-submitted bugs. It seems to me that one way to kill both birds with one go is a bug reporting scheme organized like a forum.
I think I would do a better job of reporting a bug and not leave important stuff out if I saw some examples of how to report a bug, to sort of get me thinking along the right lines before I filed my report.
Re:Bug Tracking
Great work men.
Now we are getting somewhere.
Does anyone know of a reliable bug tracker we could use or should John & Jester go ahead and set up something for people to try.
I am sure we can give anything they come up with a good tryout (just look at simpleforum) and eventually settle on one.
I must remember to suggest more unpopular programs for future projects.
Now we are getting somewhere.
Does anyone know of a reliable bug tracker we could use or should John & Jester go ahead and set up something for people to try.
I am sure we can give anything they come up with a good tryout (just look at simpleforum) and eventually settle on one.
I must remember to suggest more unpopular programs for future projects.
Well creating a PHP/MySQL reporting script would be fairly simple.
Table layout would be
| BugID | DATE | Category | Software | Description | SubmittedBy | Disposition | DispositionNotes|
Category could be used to determine whether the issue is hardware related(Drivers), Software conflicts, etc. Software would describe which piece of software is at issue. Then Description would describe the issue.
Disposition would be for the developer side to determine the status of the bug. For instance when a person submits a bug it would automatically set as active. Then when a developer reviews the bug, they could change the status "Under Review" and when the bug is fixed it could be changed to "Corrected"
Just a thought. I have not given alot of thought into the actual design but this could be a basis for the bug tracking.
With this Schema the submitter would only have to worry about filling out 4 fields on a form.
As for reviewing bugs, we could create a search function in addition to "stock" reports that would show all "active" bugs.
Just my $ .02
Jess
Table layout would be
| BugID | DATE | Category | Software | Description | SubmittedBy | Disposition | DispositionNotes|
Category could be used to determine whether the issue is hardware related(Drivers), Software conflicts, etc. Software would describe which piece of software is at issue. Then Description would describe the issue.
Disposition would be for the developer side to determine the status of the bug. For instance when a person submits a bug it would automatically set as active. Then when a developer reviews the bug, they could change the status "Under Review" and when the bug is fixed it could be changed to "Corrected"
Just a thought. I have not given alot of thought into the actual design but this could be a basis for the bug tracking.
With this Schema the submitter would only have to worry about filling out 4 fields on a form.
As for reviewing bugs, we could create a search function in addition to "stock" reports that would show all "active" bugs.
Just my $ .02
Jess
Well, Ian, you got the ball rolling--even if it did change direction. 
phpBB was an excellent choice for the forum, John. I've been looking around on the phpBB website. It is well supported and has a huge number of add-ons available. Several look like candidates that might be useful in integrating a bug report/tracker into this forum, and several more just looked like good ideas. In the hope that it might be of some help, I'll post some of them here.
In the general utility category, there are Spelling Cow, Topic Search, FAQ Editor, phpBB Search Engine Indexer, and Save Posts as Drafts. Some of which may already be incorporated in this forum.
The ones that looked like they might be useful in cooking up a forum for reporting bugs are: Configuration Map, Topic Posters, Regmod (which looks particularly interesting,) Categories Hierarchy, Topic Description, Tabulated Survey@Topic Head, Topic Display Order, and Split Topic Type.
There are hundreds more mods and add-ons on the phpBB website mods page.
phpBB was an excellent choice for the forum, John. I've been looking around on the phpBB website. It is well supported and has a huge number of add-ons available. Several look like candidates that might be useful in integrating a bug report/tracker into this forum, and several more just looked like good ideas. In the hope that it might be of some help, I'll post some of them here.
In the general utility category, there are Spelling Cow, Topic Search, FAQ Editor, phpBB Search Engine Indexer, and Save Posts as Drafts. Some of which may already be incorporated in this forum.
The ones that looked like they might be useful in cooking up a forum for reporting bugs are: Configuration Map, Topic Posters, Regmod (which looks particularly interesting,) Categories Hierarchy, Topic Description, Tabulated Survey@Topic Head, Topic Display Order, and Split Topic Type.
There are hundreds more mods and add-ons on the phpBB website mods page.
-
Jesse
Bug tracking
Hi,
Bug tracking is not a new thing, you don't need to create one, these things are a very good idea and theres lots of free ones out there.
these ones I found very quickly use php:
http://bugsonline.sourceforge.net/
http://phpbt.sourceforge.net/shots/
Jesse
Bug tracking is not a new thing, you don't need to create one, these things are a very good idea and theres lots of free ones out there.
these ones I found very quickly use php:
http://bugsonline.sourceforge.net/
http://phpbt.sourceforge.net/shots/
Jesse
-
Guest
Re: Bug tracking
The Puppy Linux group will probably continue to grow in size and there may come a time when the current informal system of bug tracking can't keep up with everything. We have used Bugzilla with Suse & it seems to be an effective way to keep track of the bugs and make sure they are squashed before the next release. There may be some things you don't like but you get used to it & perhaps contribute to making it better.
i think an important critereon for a bug tracker is that it is easy and simple for a TC person to report a bug
i looked at the firefox script that starts Firefox, and it was obvious what the problem was ... there was a line in the script that added file:// to the filename ... the bug was, it only added file:// to filenames that had a relative path ... like ../readme.txt
the fix was trivially easy, so i fixed it, and reported it to the old old Puppy forum ... Barry reported the bug to bugzilla
( i posted my bugfix to that bug report, using an id and password from bugmenot )
that was for Firefox 1.0 ... they've released Firefox 1.0.1, Firefox 1.0.2, Firefox 1.0.3, Firefox 1.0.4, Firefox 1.0.5, Firefox 1.0.6, and Firefox 1.0.7 and every version still has this bug, which is a simple and obvious logic error and trivially easy to fix
my Firefox 1.0.7 installer dotpup includes my bugfix (for the en_US and en_GB versions ... i did not patch the other languages)
there's another bugzilla threadhere
one bugzilla report is marked Status: UNCONFIRMED ... the other is marked Status: RESOLVED ... it does not seem to be resolved, and as for being unconfirmed, it seems to me it's bleedin' obvious ... like the parrot that wouldn't "voom" if you put four thousand volts through it
the point being, Mozilla may be open source, but it's about as closed as you can get if you're trying to get a bug fixed
a long time ago, the Firefox script was changed, and if you had the rox Run Action for html files set to open with Firefox ... it did nothing, nothing happenedI was gonna post a bug on bugzilla (about Mozilla)
i looked at the firefox script that starts Firefox, and it was obvious what the problem was ... there was a line in the script that added file:// to the filename ... the bug was, it only added file:// to filenames that had a relative path ... like ../readme.txt
the fix was trivially easy, so i fixed it, and reported it to the old old Puppy forum ... Barry reported the bug to bugzilla
( i posted my bugfix to that bug report, using an id and password from bugmenot )
that was for Firefox 1.0 ... they've released Firefox 1.0.1, Firefox 1.0.2, Firefox 1.0.3, Firefox 1.0.4, Firefox 1.0.5, Firefox 1.0.6, and Firefox 1.0.7 and every version still has this bug, which is a simple and obvious logic error and trivially easy to fix
my Firefox 1.0.7 installer dotpup includes my bugfix (for the en_US and en_GB versions ... i did not patch the other languages)
there's another bugzilla threadhere
one bugzilla report is marked Status: UNCONFIRMED ... the other is marked Status: RESOLVED ... it does not seem to be resolved, and as for being unconfirmed, it seems to me it's bleedin' obvious ... like the parrot that wouldn't "voom" if you put four thousand volts through it
the point being, Mozilla may be open source, but it's about as closed as you can get if you're trying to get a bug fixed
our way to track bugs
Hi,
just wanted to share the way we track bugs in Wrike . The tool allows bug tracking via eamils. I make a screen shot, paste it into an email and send it to our tester. The bug gets among our shared tasks in Wrike and we track it together. This way seems easier than any other.
just wanted to share the way we track bugs in Wrike . The tool allows bug tracking via eamils. I make a screen shot, paste it into an email and send it to our tester. The bug gets among our shared tasks in Wrike and we track it together. This way seems easier than any other.