Entrance Criteria
When a Feature Candidate has been approved by WG or TSC vote in the Stage One: Candidate process, the Chair of that group shall have done the following:
- Entered the Feature submission into the relevant Feature backlog(s)
- Updated the Feature Design document’s “current status” to Feature Design
- Notified the TSC about the new Feature approval both in the next TSC meeting and on the TSC mailing list
Cross-cutting Candidates
Feature Candidates whose scope covers more than one WG shall have an initial decomposition or work breakdown effort to create separate Epic entries in each WG’s backlog. This effort shall fall under the responsibility of the TSC.
Work Breakdown (high-level design)
The WG Chair or designee shall lead the work breakdown within their WG according to their standard practices. This shall include the creation of issues, prioritization of the tasks, and assigning resources. To assist in the effort, the author(s) shall be invited to attend the WG meetings in order to answer any questions about the User Outcomes and potentially identify additional resources, if required, to accelerate Feature delivery.
Author and Sponsor Availability
The author(s) and Sponsors may need to be consulted periodically throughout Stage Two and are advised to make themselves available upon request.
Code release frequency
Individual atomic functionality may be committed and merged, thus made public, as it is completed. This functionality, or sub-feature, shall be activated through feature flags, but shall be deactivated by default until the User Outcome is completed.
Feature promotion criteria
Once all User Outcomes are met, completed, and made public, the Feature’s status shall be deemed Supported, and the Feature Design will be promoted to Feature Support.