redhat-developer / redhat-developer/vscode-xml

Preparations for a 1.0.0 release

Open
#868 1 comment 0 reactions 2 assignees View on GitHub

@datho7561 is already working on this.

Since Jan 30, 2023.

Dominant language
TypeScript
Stars
328
Forks
101
Avg merge
1d 17h
Merged PRs (30d)
7

Description

In the past while, we've gotten a lot of really great features into the extension. Many from the language server, and a lot of integration into the extension itself. More up to date vscode-languageclient, more uniform support across marketplaces (soon), RelaxNG, new formatter, out-of-the-box support with the binary server on supported platforms, eventual migration to GH actions. I think we should start to consider what needs to happen for a 1.0.0 (mature) release.

This might involve a lot of different things :

  • evaluating what we should keep as internal/provisional vs. becoming API
  • How we address/respond to critical issues
  • looking at improvements to our release process
  • whether these changes may hurt/benefit other consumers of our work

Would be good to hear people's thoughts on this. Are there any sets of features severely lacking ? Is there any reason to continue to stay in the preview mode ? See https://devblogs.microsoft.com/visualstudio/new-preview-label-for-visual-studio-extensions-2/ .

We could use the time after 0.24.0 to work towards this.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.