Clojurians Log v2

I suppose I can maintain local metadata for my own stability reference. So I know the version I can roll back to that was consistent for however long I was using it.

I always update to the latest version every time a new release appears, so when I hit a problem, I generally know I can just roll back to the previous version. Do you not update your extensions often @lambeauxworks?

As often as VSCode prompts for updates. So maybe once every two weeks?

Hmm, I see new versions of at least one extension almost every day, and I reload the window every time. That's why I start my REPL from the terminal rather than jack-in -- so my REPL survives extension updates and window reloads 🙂

But that drop-down will show you all the versions you have installed, I think, rather than all versions, so even if you only update occasionally, I think the drop-down will show whatever was the previous version you had installed. Maybe Peter can confirm that?

I don't know. I install all released Calva versions so for me it would be the same list. 😀

Does calva have a preview release branch vs a stable release branch? Would that help or just add noise?

In theory it has, but the VS Code Marketplace does not support the versioning of Calva’s prereleases. The team has said they are fixing it for several years now. 😃 I haven’t bothered beyond that because I am a bit worried about the noise you mention. Mostly when there is something big and scary I have in the pipeline there is not much interest in testing it before it is released. So we test in production. Maybe that’s how God intended it.

Hey as long as rollback works and there's a self service path on the user side to remediation that's totally fine

How's calvas automated test suite?

As long as users are aware, they can very easily switch to whatever Calva version.

It's easy to install any previous version of an extension in VS Code. In Extensions view, click on the ⚙️ next to the extension and select Install Specific Version... and select from the drop-down:

How do you know the last "stable" point?

Those are all supposed to be stable points.

The automated test suite is lacking. Lol.

Even if stuff breaks in a new version @pez is really good at fixing it in the next version a few days later 😄 gratitude

But what we have in terms of unit tests and integration tests serves us pretty well. It most often manages to catch catastrophic things before they hit users.

The few times I have had something so big and scary under development that it holds me from releasing for fear of regression, it has been rare that holding off has been the right solution. But we need to improve the rollback process and scripts we have with Calva. Or, actually have rollback processes and scripts, would be a good start. That makes it easier to make the right call (ship it).