I don't think the doc generator runs automatically at the moment -- and,
for a while, it was having problems processing several Contrib repos
(java.jdbc still shows 0.7.10-SNAPSHOT in the generated docs, but 0.7.11
was released a while back).
On Sat, Mar 14, 2020 at 10:21 AM Matching Socks
(A constructive note) The core.async official API docs are still labeled
"core.async 0.7.560-SNAPSHOT (in development)".
I followed the link from https://github.com/clojure/core.async .
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to
I think you are misinterpreting what people believe the 0.x to 1.x means.
In the wide world of semver, 0.x indicates "unstable" and 1.x indicates
"first stable"- you're conflating that special case with a general n.x to
n+1.x which is interpreted as "breaking change". (See https://semver.org/
That ship done sailed already today... many Contrib libs hit 1.0.0 (or
1.0.x) and most of the rest will follow suit in the next several days I
expect!
I certainly plan to bump tools.cli and, with Fogus' help, core.cache and
core.memoize to 1.0.0. java.jdbc will likely remain at 0.7.11 since its
Dear August Forum: Today I noticed a new post on "Inside Clojure"
https://insideclojure.org/2020/02/18/lib-version/ , which says, after some
thoughtful justification, "we have lots of libraries in the Clojure
ecosystem that have been around for many years, are widely used, have
stable APIs,
