Introducing Flow Feature Phases (3Fs)
Open
Nobody has claimed this yet.
Feature
Feedback
Needs Definition
Needs Estimation
- Dominant language
- Go
- Stars
- 361
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
Stage 1 - 5 for Flow features - Consistency for how we think about phases of features
- maturity
- stability
- documentation
- testing required (How are we testing? Who are we testing with? What is the feature phase (and corresponding level of testing required?)
Update Testing Best Practices & Requirements for Each Phase
- Communicate testing process for externals (testnet v mainnet, when, what)
WIP here
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the proposed work in pull request #139, which is linked from this issue, and compare it with the requested feature phases and testing requirements. Done means the phase definitions, maturity and stability expectations, documentation needs, and testing guidance are agreed and recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100