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 uses to decide which ones need progress sooner is the number
of votes on the ticket. Here are some quotes from him:
"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." -- Alex Miller (puredanger) on #clojure IRC log Oct 8 2014
[text] Possibly-quick suggested changes to CLJ tickets requiring authorization of a screener
[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.
[text] List of CLJ tickets needing work. For those who are interested in developing patches for Clojure, this
report likely will not be updated as often as you need to stay informed
of the latest updates. See the section "Dev patch" on the JIRA workflow wiki page for links to tickets currently needing work.