Advance RFC #0724 "Official TypeScript support" to Stage Ready for Release

[emberjs-rfcs-bot]

Advance #724 to the Ready For Release Stage

Summary

This pull request is advancing the RFC to the Ready For Release Stage.

• PR to Accepted Stage: RFC: Official TypeScript support #724

An FCP is required before merging this PR to advance.

Upon merging this PR, automation will open a draft PR for this RFC to move to the Released Stage.

Ready for Release Stage Description

This stage is complete when the implementation is complete according to plan outlined in the RFC, and is in harmony with any changes in Ember that have occurred since the RFC was first written. This includes any necessary learning materials. At this stage, features or deprecations may be available for use behind a feature flag, or with an optional package, etc.

For codebase changes, there are no open questions that are anticipated to require breaking changes; the Ember team is ready to commit to the stability of any interfaces exposed by the current implementation of the feature.

This stage should include a list of criteria for determining when the proposal can be considered Recommended after being Released.

An FCP is required to move into this stage.

Each Ember core team will be requested as a reviewer on the PR to move into this stage. A representative of each team adds a review. If a team does not respond to the request, and after the conclusion of the FCP, it is assumed that the release may proceed.

Checklist to move to Ready for Release

• Implementation is complete according to plan outlined in the RFC, with any adjustments noted in the RFC
• Any necessary learning materials have been updated
• The Ember team is ready to commit to the stability of any interfaces exposed by the current implementation of the feature
• Criteria for moving to the Recommended Stage has been filled out
• This PR has been converted from a draft to a regular PR and the Final Comment Period label has been added to start the FCP
• Each team has been added as a reviewer to the PR at the start of the FCP
  • Framework @emberjs/framework
  • Data @emberjs/ember-data-core
  • CLI @emberjs/cli
  • Learning @emberjs/learning-core
  • Typescript @emberjs/typescript-core
  • Steering @emberjs/steering

Criteria for moving to Recommended (required)

A set of criteria for moving this RFC to the Recommended Stage, following release:

• All PRs required by the RFC have been written and approved.

Track Implementation

In this case, this represents that these RFCs have been Accepted; RFC 0800 tracks the implementation plan for this meta RFC.

• RFC: Semantic Versioning for TypeScript Types #730
• RFC: Glimmer component Signature type #748
• Author Built-In Blueprints in TypeScript #776
• First-Class Component Templates #779
• Introduce new test helpers for rendering (and re-rendering) that obviate the need for get and set #785
• RFC: TypeScript Adoption Plan #800
• RFC: public types for Owner, Transition, RouteInfo #821

[wagenet]

Since this RFC is more of an RFC for a plan it probably has a slightly different advancement path than most RFCs do. Arguably this is already in the Released stage, but we probably do need to make sure we've publicly messaged it well before we put it in Recommended.

[gitKrystan]

Per TS core meeting: move to recommended. 800 is the continuation of this one.

[wagenet]

Merging since this has already been released.