The Ember venture is happy to announce that an improved RFC (“request for feedback”) course of has been applied.
As proposed in RFC #617 “RFC Levels”, RFCs will now progress by means of a number of phases that now embrace monitoring implementation, launch, and completeness of options, in addition to design:
0 – Proposed
A brand new proposal for a change to Ember or its processes that’s supplied for group and staff analysis. In sensible phrases, that is an open pull request on the emberjs/rfcs repo.
1 – Exploring
An RFC deemed price pursuing however in want of refinement. This stage is marked by labeling the opened PR as ‘Exploring’.
2 – Accepted
A completely specified RFC. Ready for or within the technique of implementation. An FCP is required to advance to this stage. This stage is marked by up to date frontmatter within the textual content of the RFC and by being merged to the primary department of the emberjs/rfcs repo. When the RFC is merged, a PR to advance to the following stage is robotically opened on the repo to offer a coordination level for implementation.
3 – Prepared for Launch
The implementation of the RFC is full, together with studying supplies. An FCP is required to advance to this stage. The development to this stage is the merging, upon profitable FCP, of a pull request updating the stage to ‘Prepared for Launch’. Upon merge, a brand new PR to advance to ‘Launched’ is robotically opened for the RFC.
4 – Launched
The work is revealed. Whether it is codebase-related work, it’s in a steady model of the related bundle(s). The stage is once more up to date by a PR altering the stage within the frontmatter. Upon merge, a brand new PR to advance to ‘Advisable’ is robotically opened for the RFC.
5 – Advisable
The characteristic/useful resource is really helpful for normal use. An FCP is required to advance to this stage. Upon efficiently FCP, the PR to advance will probably be merged by the staff. At this level, the RFC course of is full.
Every stage is a checkpoint within the progress of a characteristic or change. The RFC repository now has automation to open a pull request to the following stage, the place applicable. These pull requests will probably be used to trace implementation and the work crucial for a characteristic to succeed in Advisable standing.
The RFC course of is method we design, implement, and shepherd adjustments and options added to the Ember Undertaking. It impacts your complete group. Please familiarize your self with the brand new course of by consulting the revamped and up to date README for the emberjs/rfcs repo.
The revised course of streamlines and unifies our current course of by bringing all of it to at least one system. It additionally will increase transparency by transferring beforehand closed course of to the open on Github.
Study extra in regards to the motivation and detailed specification of this new course of by consulting RFC #617. See an instance of the brand new course of as we tried it out to implement this very RFC: Pull Request to advance RFC #617 to Stage Prepared for Launch, Pull request to advance #617 to Stage Launched, Pull Request to advance #617 to Advisable.
We’re working to back-fill phases to earlier merged RFCs, and that work is likely one of the standards for RFC #617 to attain the Advisable stage.
