Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guideline for developing beta features/api in main branch #22055

Open
jeremymeng opened this issue May 31, 2022 · 2 comments
Open

Guideline for developing beta features/api in main branch #22055

jeremymeng opened this issue May 31, 2022 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.

Comments

@jeremymeng
Copy link
Member

jeremymeng commented May 31, 2022

When we have preview features in main branch for a package that is not ready for GA, we need to do extra work to publish stable version of the same package. Some approaches used so far:

  • release GA version from a servicing/hotfix branch that based on a commit prior to the preview feature was introduced. Sometimes this involves cherry-picking engsys fixes to pipelines etc.

  • Temporarily remove or hide the preview feature, publish stable version, then add/re-surface preview feature back

  • tag api with @beta release tag. Api-extractor can generate public version and beta version of type definition rollup files. We need additional work to publish package with the correct version.

We are looking for a strategy that allows us to develop, maintain, and release both GA and beta preview versions easily from main branch.

Some ideas that were brought up:

  • introducing a third category of package with -plusbeta suffix, which are for GA stable features plus some @beta experimental apis. This is meant to be different from our current beta packages which are for previewing features (not marked with @beta) we are going to GA. How much different is this from our current beta packages?
@jeremymeng jeremymeng added EngSys This issue is impacting the engineering system. Client This issue points to a problem in the data-plane of the library. labels May 31, 2022
@jeremymeng jeremymeng self-assigned this Sep 30, 2022
Copy link

Hi @jeremymeng, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 31, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 31, 2024
@jeremymeng jeremymeng reopened this May 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.
Projects
None yet
Development

No branches or pull requests

1 participant