… repo It is in my personal Dropbox account now, for easier synchronization across multiple machines than doing it manually. The names and email addresses are still publicly available to anyone in Clojure JIRA attachment files, and for patches that have been committed to Clojure, in the git commit history of Clojure, also available to the general public. If you want your email address to remain private, don't put it in public. "Three people can keep a secret, if two of them are dead." Benjamin Franklin
Also update next Clojure release version from 1.7 to 1.8, now that 1.7 has been released.
Even better would be to retry with a larger value automatically when it is not large enough, but I'm not that fancy yet.
Just extra noise that makes diffs from one report generation time to another unnecessarily verbose.
where N is the actual 'next release', thus making N+1 the 'next after next release'.
because recently the number of such tickets went over 2000.
Absolute vote counts, i.e. not weighted, are also used by ticket evaluators, when deciding which tickets to consider.