Reports on status of Clojure tickets

Top tickets by votes (weighted)

The links in the table below lead to lists of top open tickets by weighted vote, and tickets with no votes, for different Clojure projects.

Note for those who think that voting on Clojure JIRA tickets doesn't matter: While that may have been true pre-2013, Alex Miller's job (one of them) is to make Clojure JIRA tickets make progress.  One way he and others use to decide which ones need progress sooner is the number of votes on the ticket.  Here are some quotes:

"In particular I use votes to decide what gets triaged.  We also used votes as a way to see which issues needed to be kept in [Clojure] 1.7 this week vs pushed off to 1.8.  So I'm telling you (as the one that makes those decisions), that it's useful. I look [at] those numbers every day."

"Both CLJ-1568 and CLJ-1561 have a lot of upvotes.  If somebody will add some good tests I will screen them today or over the weekend."

Other reports

• [html] Contributing FAQ
• [html] Contributing to Clojure.  Contains links to many JIRA query results.  For contributors, note especially the "Needs Patch", "Incomplete", and "Vetted" reports.
• [text] Prescreened patches for CLJ tickets.  Now that Alex Miller is staying on top of Clojure tickets, this report is not so useful, and will not be updated very frequently.  See the date at the top for when it was last generated.  It is still useful to generate, because there is other double-checking done while generating it to let me (Andy Fingerhut) detect thing like the following, which I either correct, or report in a comment on the ticket:
  • patches that no longer apply cleanly to the latest Clojure master (due to commits to Clojure)
  • patches that apply cleanly, but Clojure fails to build or pass tests after they are applied
    
  • tickets with attributes that don't correspond to any state in the JIRA workflow
  • tickets with patches but the Patch attribute hasn't been set properly, etc.