Fork me on GitHub
#clojure-dev
<
2023-08-16
>
Jim Newton14:08:34

I provided a bug fix back in 2021, and I see that it has not been encorporated into clojure 1.11.1 https://ask.clojure.org/index.php/10897/is-this-a-bug-in-cl-format?show=10897#q10897 Did I do something wrong?

seancorfield16:08:25

I won't speak for the core team's priorities but they tend to tackle things that have more "ask" votes first so I suspect an edge case in cl-format is considered pretty low priority. Looking at the JIRA, it shows "triaged", a patch with "code and test", but priority "minor", so they've just been dealing with bugs that affect more people. Sometimes patches take a while to get incorporated (years, and multiple releases, if they're not affecting many people).

seancorfield16:08:15

(but, hopefully, this thread will at least get you an answer to your Q in JIRA about the regression test)

2
Jim Newton17:08:12

do bug fixes have risk assessments? or effort assessments?

andy.fingerhut19:08:19

I believe for ones that the Clojure core development team has spent noticeable amount of time doing design work to evaluate, they have effort assessments. These are private to their team, not published. You can see examples of this in this talk by Rich Hickey: https://github.com/matthiasn/talk-transcripts/blob/master/Hickey_Rich/DesignInPractice.md

andy.fingerhut19:08:00

Contributing to Clojure core is often an exercise in patience, is I believe a fair statement.

😅 2
andy.fingerhut21:08:44

Publicly, bug fixes have exactly what you can find out about them in the JIRA ticket and/or http://ask.clojure.org questions related to them.

andy.fingerhut21:08:01

Privately, I have no idea what additional information might be tracked about them.

Jim Newton14:08:17

I encountered the same bug today, and it took me a while to realize it was the same one, as I supposed the old bug one was no longer an issue.