And I thought we had it bad with the whole Brexit saga over here :-). On 9 November 2016 at 12:23, Mikera <mike.r.anderson...@gmail.com> wrote: > Given recent events, I advise caution when it comes to relying on votes to > make important decisions. > > On Tuesday, 8 November 2016 23:33:43 UTC+8, Alex Miller wrote: >> >> In the spirit of the US election today, I thought I would mention voting >> on Clojure tickets. Clojure manages bugs and enhancement requests in JIRA. >> Anyone can create a JIRA account and vote on open tickets in the system (no >> contributor agreement is required to vote). >> >> In the core team, we look at votes on tickets to be aware of what the >> community cares about and as one input to the order in which tickets are >> considered. However, the most-voted tickets in the system have fewer than 30 >> votes and I suspect that there are many thousands of people with opinions >> about which of these tickets are important. >> >> If you'd like to see the lists of the highest voted tickets in the system, >> you can do so in these reports: >> - Highest voted defects >> - Highest voted enhancements >> >> Andy Fingerhut also has a weighted voting report that updates about once a >> week. This show a different perspective - I'm not sure which is more useful >> but I look at both. >> >> If you'd like to learn more about the process: >> - Overview of contribution links >> - JIRA workflow >> - A blog I wrote describing the process >> >> A few examples of highly voted issues that have been included in 1.9 so >> far: >> - CLJ-1224 Records do not cache hash like normal maps (21 votes) >> - CLJ-1298 Add more type predicate fns to core (18 votes) >> - CLJ-1744 Unused destructured local not cleared, causes memory leak (17 >> votes) >> - CLJ-1242 = on sorted collections with different key types incorrectly >> throws (7 votes) >> - CLJ-401 Add seqable? predicate (7 votes) >> >> Alex >> >> >> > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
