Advance RFC #1027 "EmberData | SchemaService" to Stage Ready for Release#1030
Advance RFC #1027 "EmberData | SchemaService" to Stage Ready for Release#1030kategengler merged 2 commits intomasterfrom
"EmberData | SchemaService" to Stage Ready for Release#1030Conversation
emberjs-rfcs-bot
added
RFC Advancement
S-Ready for Release
|
@runspired this one also could use filling out. |
|
Merged, will go out in 5.4. |
|
This should probably advance since it sounds "ready for release" but we should double-check the criteria. |
|
@runspired What is the status of this? |
|
we should update the text before advancing to reflect a few field schemas that were added after the original RFC was merged. There may also be some updates to the mechanics of what to do when a schema is missing that we'll want to fill in here. There's a category of schema fields that is not yet supported around mutable derivations, primarily for shortening long paths. There is an open question as to whether some of this can be solved by enabling arbitrary schema fields to work: warp-drive-data/warp-drive#9534 |
|
This is in fact released and should instead be waiting to be Recommended. |
|
This is ready to merge but GitHub does not seem to be working to merge. |
kategengler
force-pushed
the
advance-rfc-1027
branch
from
e7cb2ff to
940d18b
Compare
4 participants
Advance #1027 to the Ready For Release Stage
Rendered
Summary
This pull request is advancing the RFC to the Ready For Release Stage.
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
Final Comment Periodlabel has been added to start the FCPCriteria for moving to Recommended (required)
A set of criteria for moving this RFC to the Recommended Stage, following release:
we should update the text to reflect a few field schemas that were added after the original RFC was merged. There may also be some updates to the mechanics of what to do when a schema is missing that we'll want to fill in here.
There's a category of schema fields that is not yet supported around mutable derivations, primarily for shortening long paths. There is an open question as to whether some of this can be solved by enabling arbitrary schema fields to work: spec: can we make SchemaRecord support arbitrary schema fields? warp-drive-data/warp-drive#9534
Track Implementation
<-- Use this section to track implementation of the RFC -->