We'd like to create a vehicle for experimental branches that get merged into a temporary branch based off of master on a nightly basis, and published to npm. Presumably it'd be called something like typescript@experimental.
Users can use this branch to more-easily play with experimental features. This will allow us to keep branches in a reasonable state as they wait for the "feature" period of our release cycle, and will allow us to see how those features combine and interact.
This is a partial alternative to #28152 - the main difference being that
- this allows features to not be merged into
master
- experimental features aren't flagged because they're not even part of nightly
We'd like to create a vehicle for experimental branches that get merged into a temporary branch based off of
masteron a nightly basis, and published to npm. Presumably it'd be called something liketypescript@experimental.Users can use this branch to more-easily play with experimental features. This will allow us to keep branches in a reasonable state as they wait for the "feature" period of our release cycle, and will allow us to see how those features combine and interact.
This is a partial alternative to #28152 - the main difference being that
master