Logtalk Ticketing Guidelines
Checks to perform before opening a bug ticket
- Check that no ticket is already filed on the same bug.
- Check that you can reproduce the bug using the latest stable versions of both Logtalk and your Prolog back-end compiler.
- Check that the bug is not specific to a Prolog back-end compiler. Try to reproduce the problem using a different Prolog compiler.
- Check (if possible) that the bug is not operating-system specific.
- Check the release notes of the latest Logtalk development version. If the bug is listed as fixed in the current development version, checkout (if possible) the development version and retest.
- Check the Logtalk FAQ.
Opening a bug ticket
- Provide a detailed description of the bug. Include any information that might be relevant for developers reading the ticket.
- Provide detailed information on your Logtalk setup and running environment, including version numbers of Logtalk, of the Prolog back-end compiler, and of the operating-system.
- Provide detailed steps on how to reproduce the problem. Attach to the ticket any code fragments that illustrate the problem.
- Provide an email address that allows the Logtalk developers to contact you for further details about the bug.
Ticket keywords
Some of the keywords you may use when creating a ticket are:
- threads (multi-threading features)
- dcgs (DCGs implementation)
- encodings (support for different text encodings)
- events (event-driven programming support)
- categories
- inheritance
- performance
- portability
- debugging
- profiling
- testing (unit testing)
- configs (back-end Prolog compiler configuration files)
- settings (settings files)
- posix
- windows
- macosx
- linux
- debian
