[Feat]: Upgrade Vscode to 1.76

[balajib-b]

What is your suggestion?

Why do you want this feature?

Are there any workarounds to get this functionality today?

Are you interested in submitting a PR for this?

[benz0li]

@code-asher Will there be a "March 2023" milestone?

[benz0li]

@code-asher Is Joe Previte is no longer involved in this project?
👉 If so, who has the lead now and what does the future [of this project] look like?

[benz0li]

vscode 1.76.1 has been released:

@code-asher Consider taking a .2-release as base for a new code-server release.
ℹ️ .0-releases have had some fundamental bugs.

i.e.

1. use the .1-release as base for a release candidate (RC)
2. test, debug and fix; maybe do another RC-release
3. update codebase to the .2-release
4. test, debug and fix
5. release

– #6004 (comment)

[bala]

@code-asher like @benz0li mentioned, it would be nice if we could work on a milestone for each month. This would also give us transparency on the development progress in code-server.

In recent weeks we see that the repo activity has reduced so much. May be due to the piling up of other works for the team.

Could you also let us know the scope of the code server? And the coder's best interest in keeping the code server alive and updated?

[code-asher]

Sorry all, I was unexpectedly out last week.

Joe is no longer involved, at least as a maintainer (his farewell is here for those interested: #6031).

Maintenance falls to me and while we do have a vested interest in keeping code-server updated since we use it ourselves I think it is unlikely we will do much more than update VS Code, handle any PRs that folks might open, and triage issues/discussions.

If we had more activity I think grooming milestones would make sense but since there will only be VS Code updates I am not sure it makes sense to spend the effort.

I will try to get us updated today.

[benz0li]

Maintenance falls to me and while we do have a vested interest in keeping code-server updated since we use it ourselves I think it is unlikely we will do much more than update VS Code, handle any PRs that folks might open, and triage issues/discussions.

@code-asher Thank you for the clarification. I am satisfied with the current features (base path, local storage, proxy url, etc.) and keeping the software up to date is fine with me.