rokucommunity / rokucommunity/vscode-brightscript-language

Support for beta releases

Open
#339 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
132
Forks
60
Avg merge
13h 53m
Merged PRs (30d)
20

Description

VSCode doesn't currently support beta releases, but according to https://github.com/microsoft/vscode/issues/15756 it might be coming soon. However, that fix requires us to play games with our release version numbers since the vscode extension marketplace doesn't support prerelease data in version numbers. I'd rather not have to do things like "even minor numbers mean primary release, odd minor numbers mean prerelease".

Here are the options right now as I see them:

  1. Do nothing. If people want to try a prerelease version, they will just manually download and install the vsix from our releases page. The downside is, users must manually install every upgraded version after this.

  2. A hybrid of option 1 where we add code to the prerelease extension that checks for new versions and auto-updates behind the scenes. The downside is, that logic is already build into the vscode extension flows anyway, so we'd be re-inventing the wheel and running custom code.

  3. Install a separate "BrightScript Language (Insiders)" channel to the extension store. The downside is that we'd have two store versions which might get confusing and clutters up the store.

  4. Use the new insiders extension feature added in https://github.com/microsoft/vscode/issues/15756 and leverage the even/odd minor version pattern.

  5. Wait 12-18 months for the extension marketplace to support prerelease semver patterns, and then implement https://github.com/microsoft/vscode/issues/15756.

    https://github.com/microsoft/vscode/issues/15756#issuecomment-916728348 (Long term 18 months (upstream dependency): MarketPlace will add support for pre-release versions)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files or tests. Start by reviewing the linked VS Code prerelease discussion and the extension's existing release and Marketplace flow. Done would require choosing and implementing a supported prerelease distribution strategy, with versioning and upgrade behavior defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.