Fork me on GitHub
#cljdoc
<
2022-04-10
>
Cora (she/her)19:04:09

totally understand if you haven't had time to look

lread19:04:22

I just tried a minute ago @corasaurus-hex and it works!

Cora (she/her)19:04:26

but I'm sitting down to code and thought I'd do some housework

lread19:04:29

Please do merge away!

Cora (she/her)19:04:49

merged! 💜

gratitude 1
Cora (she/her)19:04:23

totally an aside but I just noticed we don't have a changelog

Cora (she/her)19:04:28

maybe that ship has sailed

lread19:04:01

Yeah true. I’m ok with commit log for cljdoc… but it doesn’t exactly let our users know what’s new and noteworthy.

Cora (she/her)19:04:55

linking the PRs in the changelog is super helpful, too. you can get context on each change

Cora (she/her)19:04:36

@pez does that on calva and it's been really helpful for going back through changes to understand context

Cora (she/her)19:04:52

maybe when we have time

Cora (she/her)19:04:53

¯\(ツ)/¯

Cora (she/her)19:04:58

or maybe next PR!

lread19:04:46

Since we release on merge to master, we’d need something/someone to encourage a changelog is actually updated.

lread19:04:58

By our ragtag team!

lread19:04:16

For bigger features the ADRs help with rationales. (but again for devs, not for end users).

lread19:04:54

Our ragtag mascot? simple_smile

lread20:04:26

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.