In addition to bug reports, you should also open a ticket if you have
some new code which extends Sage's capabilities. If you have a
feature request, start a discussion on sage-devel first, and
then if there seems to be general agreement that you have a good idea,
open a ticket describing the idea.
Other comments:
- Before opening a ticket, make sure that nobody else has opened a
ticket about the same or closely related issue.
- It is much better to open several specific tickets than one that
is very broad. Indeed, a single ticket which deals with lots of
different issues can be quite problematic, and should be avoided.
- Be precise: If foo doesn't work on OS X but is fine on Linux,
mention that in the title; also use the keyword option so that
searches will pick up the issue.
- The problem described in the ticket must be solvable. For
example, it would be silly to open a ticket whose purpose was ``Make
Sage the best mathematical software in the world''. There is no metric
to measure this properly and it is highly subjective.
Release 2008.09.17, documentation updated on September 17, 2008.
See About this document... for information on suggesting changes.
