This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-10
Channels
- # announcements (16)
- # asami (7)
- # aws (5)
- # beginners (46)
- # calva (47)
- # clj-kondo (3)
- # cljdoc (23)
- # clojure (70)
- # clojure-germany (1)
- # clojurescript (6)
- # community-development (2)
- # datomic (3)
- # emacs (14)
- # exercism (5)
- # hyperfiddle (4)
- # jobs (1)
- # kaocha (9)
- # lsp (13)
- # malli (6)
- # membrane (11)
- # off-topic (22)
- # pedestal (4)
- # portal (19)
- # quil (3)
- # reagent (8)
- # remote-jobs (1)
- # shadow-cljs (48)
- # spacemacs (5)
@lee how are you feeling about https://github.com/cljdoc/cljdoc/pull/575 ?
totally understand if you haven't had time to look
I just tried a minute ago @corasaurus-hex and it works!
but I'm sitting down to code and thought I'd do some housework
sweet!
totally an aside but I just noticed we don't have a changelog
maybe that ship has sailed
Yeah true. I’m ok with commit log for cljdoc… but it doesn’t exactly let our users know what’s new and noteworthy.
linking the PRs in the changelog is super helpful, too. you can get context on each change
@pez does that on calva and it's been really helpful for going back through changes to understand context
maybe when we have time
¯\(ツ)/¯
or maybe next PR!
Since we release on merge to master, we’d need something/someone to encourage a changelog is actually updated.
For bigger features the ADRs help with rationales. (but again for devs, not for end users).
Yeah maybe not for that changelog…(?) we link to a https://github.com/cljdoc/cljdoc/blob/master/doc/roadmap.adoc#new-storage-backend from http://cljdoc.org and well… it is pretty out of date. I expect the same would happen with a changelog. Maybe.