Bug ReportingFound a bug in Helma? The best way to get it fixed is to file a bug report with our Bugzilla system. When writing a bug report, it's a good thing to remember that the person reading it does not know what you were about to do. Please add as much context and information as possible! At least the following info should be included:
Ideally, a bug report should include code to reproduce the behaviour, but of course that's not always a trivial task. If filing a bug with Bugzilla seems like too much work, you can also send a report to one of the mailing lists. Messages to the list tend to vanish in the archives, though, while bug reports don't, so chances of getting things fixed are usually higher with a proper report. |
navigation
Download
Community
Weblog
Mailing Lists
IRC Channel
Documentation
Introductions
Tools
Reference
Project
Roadmap
Bug Reporting
Source
Wiki
Tags
Updates
Related Projects
Sites using Helma
Shop
search
all tags
Tagsapps (1) bugs (2) class (1) community (2) compatibility (1) concurrency (1) continuations (2) Documentation (4) Documentation ORM (1) dogfood (1) formatting (1) gobi (1) helma (6) helma 1.6 (13) helma 1.7 (8) helma 2 (13) helma ng (7) hopobject (1) html (1) inheritance (5) introspection (1) java (2) javascript (5) jetty (1) JSDoc (1) lazy (1) marius person (1) metaprogramming (2) modules (3) oop (1) organization (2) ORM (1) parsing (1) project (2) projects (1) prototype (1) Rabbit (2) REPL (1) rhino (4) roadmap (3) shell (1) shop (0) Skin Rendering (5) Snippets (1) source svn (1) sugar (3) templates (13) testing (4) Tobi (7) tobi repl shell introspection (0) xml (1) Pages linking to this page: Wiki Overview Text Draft |