|
|
|
Once approved, a feature request could transition through the following steps:
|
|
|
|
- **Approved**: Feature approved by TSC; design phase can start.
|
|
|
|
- **Design**: Feature under design; discussing on HOW to do it.
|
|
|
|
- **Development**: Design approved; feature under development/implementation.
|
|
|
|
- **Testing and Review**: Feature implemented and under review and testing by the developers and the community.
|
|
|
|
- **Completed**: Testing and review completed, and feature merged.
|
|
|
|
- **Abandoned**: Feature abandoned.
|
|
|
|
|
|
|
|
**Important**: An approved feature is not a guarantee for implementation.
|
|
|
|
Implementing a feature requires resources, and resources come from the members, participants and individual contributors integrating the TFS Community, which might have prioritized the development of other features based on their own interests and the interests expressed by the LG, the TSC, and the MDGs.
|
|
|
|
|
|
|
|
Once a Feature is mature, e.g., Testing, Review, Completed, it can be accepted for inclusion in a specific Release.
|
|
|
|
This is accomplished by including the issue ticket in the respective EPIC "_ReleaseX.Y_".
|
|
|
|
For instance, to see the Features included in Release X.Y, check EPIC "_ReleaseX.Y_". |
