Release Process

[MNASTM]

Hello,

I am wondering how the release process work. When do you plan to publish the next one on the marketplace?
I am actually interested in #749 which looks to solve one of my use cases which is:

• clangd path is not found in path at startup (=>install prompt notification)
• user does not click install but provides a valid path in the settings (clangd.path)
• clangd server restarts automatically (which is not the case with 0.1.33)

Being that said, it sounds related to on-going #117. What is the status of this one?

Thanks

[HighCommander4]

I am wondering how the release process work. When do you plan to publish the next one on the marketplace?

vscode-clangd does not currently have a regular release schedule. Releases so far have been made ad hoc by pushing a commit which bumps the version number in package.json, which triggers a Github Action that packages the source files on the master branch and uploads the package to the VSCode Marketplace.

Things are currently in a bit of a limbo, because we've had a change land which caused a serious regression and had to publish a new version to revert it on two separate occasions (#708, #722, #734). Currently the change is back on the master branch (#758) but I'd like to have a workflow in place to publish pre-release versions for validation (#765) before having it appear in a stable release again. However, I have not had time to do the RelEng work to implement such a workflow thus far. @JVApen has expressed interest in helping with this but I understand at the moment he is busy as well.

Help with the process would definitely be appreciated.

I am actually interested in #749 which looks to solve one of my use cases which is:

• clangd path is not found in path at startup (=>install prompt notification)

• user does not click install but provides a valid path in the settings (clangd.path)

• clangd server restarts automatically (which is not the case with 0.1.33)

I don't think #749 addresses this use case. #749 concerns scenarios where the user does click "install"; the change it makes is that rather than reloading the entire VSCode window after the installation, it just starts the clangd server.

Being that said, it sounds related to on-going #117.

Yes, it sounds like #117 would address your use case.

What is the status of this one?

It looks like the patch is a few years old and has bitrotted. If you're interested in the use case, you're welcome to ping the patch author on the PR, or take over the PR yourself. I'm happy to review an updated PR that applies to current master.

[JVApen]

For reference, we just managed to publish the first pre-release version of the plugin. (0.1.34)

[asadm]

Hello, is there a plan to do a normal release? Our extension depends on this fix but I cannot enforce users to install pre-release.

[HighCommander4]

Hello, is there a plan to do a normal release?

@JVApen, do you think we're ready to roll out #683 to the release population?

Our extension depends on this fix but I cannot enforce users to install pre-release.

(It's not clear to me what "this fix" refers to.)

[JVApen]

I think it is stable enough

[HighCommander4]

I think it is stable enough

Ok, I sent out #817 to create a new stable release.