This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-28
Channels
- # announcements (5)
- # asami (34)
- # babashka (15)
- # beginners (222)
- # calva (5)
- # cider (2)
- # circleci (4)
- # cljfx (11)
- # clojure (34)
- # clojure-europe (10)
- # clojure-nl (2)
- # clojure-taiwan (2)
- # clojure-uk (5)
- # clojurescript (27)
- # conjure (8)
- # cryogen (11)
- # cursive (11)
- # datomic (7)
- # depstar (6)
- # fulcro (29)
- # graalvm (2)
- # joker (3)
- # kaocha (9)
- # nrepl (4)
- # off-topic (9)
- # pathom (1)
- # shadow-cljs (11)
- # spacemacs (4)
- # sql (1)
- # tools-deps (12)
Clojure libs sometimes use x.y.commits for versions where commits are the number of commits. What do x.y stand for? Random?
@borkdude, seems to vary by project. For my projects inc in x means breaking change, inc in y means some significant change, commits is bug fixes and minor changes.
I think it makes sense what you do, although I don't see the point of using a commit count in this case, you could also just use an incremental number
True, could do that. The commit count does convey activity in the repo, and says that a release is at this commit count. But yeah, a subjective preference for sure.
My notes from the last time I looked at versioning schemes https://github.com/lread/rewrite-cljc-playground/blob/master/doc/design/01-merging-rewrite-clj-and-rewrite-cljs.adoc#library-version-scheme-in-progress