dev-tooling

oyakushev 2024-05-29T15:17:25.331909Z

Can we have a CIDER release soon? I'd like to start working on integrating the JVMTI thread stopper into CIDER, and it's best to keep that out of the upcoming major release.

bozhidar 2024-05-30T08:56:22.329449Z

Well, I can a new CIDER release even today. I don’t see anything major that’s pending or in progress currently. That being said, I guess we can give ourselves a few days and aim to do the release on Monday next week.

bozhidar 2024-05-30T13:19:11.121739Z

After reviewing the current state of affairs I just went ahead and cut 1.14. Hopefully 1.15 will happen faster. πŸ™‚

πŸŽ‰ 1
vemv 2024-05-29T15:46:23.074269Z

Soon, yes, that's the goal! Either way please try to simply keep it in a branch so that we can remove pressure

πŸŽ‰ 2
oyakushev 2024-05-29T15:51:25.872999Z

It will start in a branch, obviously, until it is merged. But the sooner it ends up in MELPA, the sooner people can start testing it.

vemv 2024-05-29T15:56:11.056569Z

It's also no issue to have it merged and disabled under a defcustom, but well documented. We've done so for other features. It can be enabled by default later without being considering a breaking change (assuming it's considered battle-tested by then).

oyakushev 2024-05-29T15:57:44.682749Z

It will be behind an off-by-default defcustom, possibly forever. I'd still probably have a stable release without it, but that works too.

oyakushev 2024-05-29T15:59:26.848629Z

However, it would either require bumping the injected nrepl dependency to a beta (because new nrepl is still in beta) which is not cool for a release. Or it will require some magic around checking a defcustom and if it's true – overriding nrepl dep (which I don't like)

oyakushev 2024-05-29T16:02:07.419359Z

So I see the ideal scenario as: β€’ Release stable CIDER β€’ Add support for JVMTI and bump injected nrepl to a beta. β€’ Let the users test it for a while. β€’ Release stable nrepl, update injected nrepl dependency to a stable version. β€’ We are in good state for next stable release whenever it will be.

πŸ‘ 1