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 #0984 "Treat Safari as an Evergreen Browser" to Stage Released #1021

Merged
merged 3 commits into from
May 10, 2024

Conversation

emberjs-rfcs-bot
Copy link
Collaborator

Advance #984 to the Released Stage

Rendered

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 26, 2024
@ef4
Copy link
Contributor

ef4 commented May 10, 2024

The policy change has landed on the website. There's a draft PR for the (related but not strictly part of this policy change) codification of the browser support numbers that will get set when 6 goes out:

ember-learn/ember-website#1110

@ef4 ef4 marked this pull request as ready for review May 10, 2024 18:39
@ef4 ef4 merged commit ee15075 into master May 10, 2024
8 checks passed
@delete-merged-branch delete-merged-branch bot deleted the advance-rfc-0984 branch May 10, 2024 18:40
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants