Clojurians Log v2

the main issue is that although we are using by git sha on clojure-lsp, there is lein-clojure-lsp which is a lein project, and with pedantic we are have version issues on clients, so we can't specify the rewrite-clj version to use there

I’ve been busy working on other projects. I’m not keen to release paredit changes in their current state. I’ll make it a priority to get back to paredit soon.

> I’m not keen to release paredit changes in their current state Why did you merge them?

?

To make them easily available for folks to experiment with.

Paredit has been a huge effort to rework. I keep learning new things as I fix things.

It's been interesting, but after a while, it's not a ton of fun. Hence, me taking a break to work on other things.

What you did recently on master really helped clojure-lsp fix their bugs and looks stable from LSP POV

If things didn’t get worse then I guess it’s safe to do a release

I'm not keen to release because as I rework paredit more behavior could still change and I'd love to not to create breaking changes.

If I had realized paredit was going to be so much work, I suppose I could have done the work in a branch off master. But this realization did not hit me early enough.

Are the changes that @ericdallo is interested in the paredit ones?

Yep

Got it.

What if a critical bug came up, we’d fix it and had to release it today?

Not ideal, but I'd have to make a choice. Could revert paredit changes and release. Or release paredit as is and pay the price later.

AFAIK the paredit changes were add new functions right? so looks safe to me

Open source is not always a fun hobby!

Yeah, but I'm not confident I won't create breaking behaviour changes in paredit... I've learned that I don't fully understand what paredit should be doing yet in some cases.

Once I get a grip on that, I'll feel better about creating a release.

Which means... I'm dragging myself back to paredit to try to finish it up enough for a release.

I guess worse case we could’ve released an alpha ;)

Yeah... I suppose... mark paredit changes as experimental and prone to change... use at your own risk... etc...

I'd buy that :)

Ha! If I bog down too much, we'll do that. But give me some more days and I'll see what I can do.

no problem, thanks for your time!