Error formatting macro: pagetree: java.lang.NullPointerException
Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

Creating Tickets

The first step in the contribution process is to open a ticket. Please do so through JIRA and not through GitHub. This ticket can be created by anyone with or without a CA. It is OK to create a ticket and submit a patch at the same time, but please be aware, if the ticket is later rejected, the time spend developing the patch will be lost. Therefore it is recommended that coding on non-trivial patches should be postponed until after the vetting process.  One possible advantage to submitting a patch before the ticket is vetted, is that it might be vetted and screened all at once by the screener, if they choose to do that, saving some time.

If you have questions about whether some behavior of Clojure is a bug, or submitting bug reports or enhancement requests, please ask on the clojure Google group.

You need an account on in order to create a ticket.  Click on the "Sign up" link near the top right of this page to do so.  If you don't see one, but instead your name, you've already got an account and you are logged in.

Qualities of a Great Ticket

All tickets should have:

  • Type: Correct categorization (Defect or Enhancement)
  • Summary: concise title
  • Description: 
    • Exactly one issue (if multiple, split across tickets and link)
    • (If Defect) Reproducible demonstration of problem (commands that can be duplicated in a repl are preferred)
    • (If Enhancement) Statement of the what should be improved 
    • Links to relevant prior discussion on clojure-dev, IRC, or email thread as appropriate
  • Priority: categorize based on impact and whether this is a theoretical issue or one actually encountered in real code

Tickets ready for screening should also have:

  • Description:
    • The cause of the problem
    • An accurate description of the approach being pursued to solve the problem
    • Name of current patch to consider
    • Summary or reference to alternative approaches that were considered
  • Patch attachment:
    • Implementation that follows the approach specified in the description
    • Tests as appropriate
    • Benchmark data (if performance related)
This is an example of how the description might look once a ticket has gone through screening - it starts with a succinct description of the problem and a demonstration that can be tried at the REPL. That may be all that exists when the ticket comes into the system. By the time it gets through screening, we should expect to see the dev's analysis of the cause of the problem, the solution that is being offered (and possibly alternatives that were considered), and the patch currently implementing the solution and test.
Adding odd numbers doesn't work. 

user> (+ 2 2)
user> (+ 1 3)

Cause:  Never implemented odd number adding in the Compiler! See the missing branch in FooExpr.

Solution:  Fully implemented the branch for odd numbers to be just like even numbers. Considered just getting rid of addition altogether but I guess people use it.

Patch: add-odd-3.patch

Tend Your Ticket

As work progresses on a ticket, it is common for it to accumulate discussion between submitter, screeners, and patch developers. As this occurs, it is essential to edit the ticket description to stay up to date as a summary of the essential problem, solution approach, and patch. It should not be necessary to read the the full ticket history to evaluate the patch.