The ClojureWerkz team recently started writing a series of blog posts about how we do things (and why). The series were started a while ago in [1]. Here's the second part, on writing useful change logs:
http://blog.clojurewerkz.org/blog/2013/09/07/how-to-write-a-useful-change-log/ If you have examples of change logs you really like (or find terrible), please reply to this thread and I will update the post. 1. http://blog.clojurewerkz.org/blog/2013/04/20/how-to-make-your-open-source-project-really-awesome/ -- MK http://github.com/michaelklishin http://twitter.com/michaelklishin -- -- 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/groups/opt_out.
