On 4/13/16, 11:50 AM, "clojure@googlegroups.com on behalf of 676c7...@gmail.com" <clojure@googlegroups.com on behalf of 676c7...@gmail.com> wrote: >Would now be a good moment to bump the major version number to indicate >clearly to all clients ‘your software may break if you make the jump’?
It jumped from 0.5.x to 0.6.0 — that’s usually how contrib libraries indicate potential breakage. Contrib libraries have a strict set of criteria to reach 1.0.0 and, last I asked the Clojure/core folks, very few of the contrib libraries are ready for that yet. If you look at the java.jdbc change log you’ll see: 0.0.7 -> 0.1.0 — removed dependency on structmap, potentially breaking order-dependent code 0.1.4 -> 0.2.0 — merged namespaces, potentially breaking code that depended on the "internal" namespace 0.2.3 -> 0.3.0 — deprecated 0.2.x API (moved it to a different namespace, breaking code), introduced new API 0.3.7 -> 0.4.0 — dropped Clojure 1.2 support 0.4.2 -> 0.5.0 — dropped Clojure 1.3 support 0.5.0 -> 0.5.5 — deprecated variadic aspects of the API 0.5.8 -> 0.6.0 — removed deprecated features Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- 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.
