> Stuart, can you elaborate a little what better triage looks like? What are > the current issues you're facing and what would make the process better for > you? The ER metaphor perhaps isn't the best :) > What are other ways the community can help get changes pushed along better > and integrated? > How might we better adjust the process to prevent patched and screened > changes from sitting around for long stretches of time?
Here are a few ideas: 1. Please be clear in marking something a defect vs. an enhancement requests. Defects have top priority, and I would guess that I reclassify 30% of the tickets I review from defect to enhancement request. 2. If you have found a defect for which you know of no workaround, shout *loudly*. Put a message on the mailing list, making it clear that you are stuck. These items should get the very highest priority. 3. If your enhancement can be library code, make a contrib library of it. Then you are not tied to Clojure's deliberately more conservative release cycle. I will put some more thought into this, and plan to host an unsession at the conj for people who want to work on it. Stu -- 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
