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

Advance RFC #0739 "EmberData | Deprecate Non Strict Relationships" to Stage Released #924

Merged
merged 4 commits into from
Jul 28, 2023

Conversation

emberjs-rfcs-bot
Copy link
Collaborator

@emberjs-rfcs-bot emberjs-rfcs-bot commented Apr 5, 2023

Advance #739 to the Released Stage

Summary

This pull request is advancing the RFC to the Released Stage.

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

Released Stage Summary

The work is published. If it is codebase-related work, it is in a stable version of the relevant package(s). If there are any critical deviations from the original RFC, they are briefly noted at the top of the RFC.

If the work for an RFC is spread across multiple releases of Ember or other packages, the RFC is considered to be in the Released stage when all features are available in stable releases and those packages and versions are noted in the RFC frontmatter.

Ember's RFC process can be used for process and work plans that are not about code. Some examples include Roadmap RFCs, changes to the RFC process itself, and changes to learning resources. When such an RFC is a candidate for Released, the work should be shipped as described, and the result should presented to the team with the intent of gathering feedback about whether anything is missing. If there is agreement that the work is complete, the RFC may be marked "Released" and a date is provided instead of a version.

An RFC is moved into "Released" when the above is verified by consensus of the relevant team(s) via a PR to update the stage.

Checklist to move to Released

  • The work is published in stable versions of the relevant package(s), with any feature flags toggled on.
  • Deviations from the original RFC are noted in the RFC
  • Release packages and dates are updated in the RFC frontmatter

@emberjs-rfcs-bot emberjs-rfcs-bot added RFC Advancement S-Released PR to move to the Released Stage labels Apr 5, 2023
@runspired runspired added the T-ember-data RFCs that impact the ember-data library label Apr 5, 2023
@runspired runspired self-assigned this Apr 5, 2023
@ef4
Copy link
Contributor

ef4 commented Jun 30, 2023

@runspired is this release now? Wondering if this is ready to advance to the next stage. Same goes for #926 and #925

@ef4
Copy link
Contributor

ef4 commented Jul 14, 2023

Updates from the weekly review meeting: this is released (and in fact removed at 5.0) and we just need to make updates here in the tracking.

@runspired runspired marked this pull request as ready for review July 28, 2023 17:56
@runspired runspired merged commit 267a831 into master Jul 28, 2023
8 checks passed
@delete-merged-branch delete-merged-branch bot deleted the advance-rfc-0739 branch July 28, 2023 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC Advancement S-Released PR to move to the Released Stage T-ember-data RFCs that impact the ember-data library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants