You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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.
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:
-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?The text was updated successfully, but these errors were encountered: