Comments:Bug Reports
[Edit]Why not a 'real' bug tracker?
I know a wiki can be use for many things, but Sometimes the specialized tool is simply better. Why not use the bug tracker provided by sourceforge. It works well, gives some structure (which I think is useful for bugs), notifies by email everyone, allow advanced queries, etc.
Note that JSPWiki is moving from wiki bugreports to bugzilla. And I think this moves is less painful when done with a limited unmber of bugs ;-)
- I agree that a bug tracker offers a lot of benefits, but there are also advantages to having everything in one place -- Ryan 23-Jul-2007 14:25 PDT
- You're right on the advantage of having everything in one place, but usually people understand quite well that bugs are at a different place than user documentation, or technical design discussions. -- Régis Décamps
- those reporting bugs are likely to come to jamwiki.org first, they won't have to register for jamwiki.org AND a bug trackign system,
- All developers are already registred within sourceforge, and other users can open tickets anonymously in sourceforge. -- Régis Décamps
- and a single check of Special:RecentChanges shows all project updates. -- Ryan 23-Jul-2007 14:25 PDT
- We can imagine defining a new Bug namespace that points to sourceforge bug tracker, and Bug:123 being added to the RecentChanges page when sourceforge sends a mail notification -- Régis Décamps
- That said, while I'd lean towards keeping bug reports on the wiki I'm not strongly opposed to using a bug tracker, so if others would prefer bug reports moved please say so and we can consider making the change. -- Ryan 23-Jul-2007 14:25 PDT
- I don't want to make you change anything if you don't prefer it yourself. But I forgot to point that bugtrackers set unique id to issues; which allows to commit code with comments similar to "fix bug 123 Adding new user account NPE when "mail.from" is not set". In conclusion, I believe there is a need to formalize bugs, this can either be build in the wiki like jspwiki did or with the integration of a bug tracker to the wiki (in particular for Special:RecentChanges and Special:Search. All that being said, il n'y a pas le feu au lac (literally, there is no fire to the Geneva Lake, i.e. there is no panic) -- Régis Décamps 24-Jul-2007 03:07 PDT
- +1 for a real bugtracker -- Luzi 25-Jul-2008 02:31 PDT
[Edit]Split Bug Reports
Should we split up Bug Reports for each version like Bug Reports/Resolved, e.g. Bug Reports/0.8.1 and Bug Reports/0.9.0? It would be easier to report and comment, I think. --hp 17-Jan-2010 04:18 PST
- The current Bug Reports page is meant to catch all bugs that affect the currently released version, but you're right that it's messy. I've actually been thinking of two possible alternatives to this page:
- Use JIRA. I like the idea of having all JAMWiki-related info on a JAMWiki platform, but there are obviously advantages to using an actual bug tracker.
- Create either a template or a form-based entry for bug reports so that version, fix, etc are included. It can then be made clear that any bug report is against the latest version.
- Any thoughts? -- Ryan • (comments) • 17-Jan-2010 09:07 PST
- JIRA is absolutly great, but everyone needs an additional account. I don't know what the best solution would be, but when bug reports stay on jamwiki.org, I would prefer a segmentation into versions or into features (database, configuration, upgrade, display,...). A template for reports would be nice too, but without segmentaion Bug Reports will additionally grow thus it (I think). --hp 21-Jan-2010 03:46 PST