Lines Matching full:and
6 For feature tracking we use Github labels to classify new features and
10 Changes to existing features that are not considered a bug and would not
16 that is not part of any release plans yet, that has not been vetted, and needs
17 further discussion and details.
20 A committed and planned unit of functionality with a detailed design and
21 implementation proposal and an owner. Features must go through an RFC process
22 and must be vetted and discussed in the TSC before a target milestone is set.
36 This is the formal way for asking for a new feature in Zephyr and indicating its
37 importance to the project. Often, the requester may have a readiness and
38 willingness to drive implementation of the feature in an upcoming release, and
42 and a proposed design or implementation.
45 - The TSC discusses new ``feature-request`` items regularly and triages them.
47 the project goals and other timeline considerations. The priority is
54 - After the initial discussion and triaging, the label is moved from
55 ``feature-request`` to ``feature`` with the target milestone and an assignee.
57 All items marked as ``feature-request`` are non-binding and those without an
58 assignee are open for grabs, meaning that they can be picked up and implemented
63 Roadmap and Release Plans
66 Project roadmaps and release plans are both important tools for the project, but
67 they have very different purposes and should not be confused. A project roadmap
69 plan is a tactical document designed to capture and track the features planned
81 project's strategic objectives and expectations.
84 can help the project present its plan in a compelling way to existing and new
85 stakeholders, to help recruit new members and it can be a helpful resource the
86 team and community can refer to throughout the project's development, to ensure
90 themes, epics, and goals.
98 and fixes that need to go into a specific release or milestone.
100 The release plan communicates those features and enhancements slated for your
103 and main stakeholders of the project can make progress on.
106 have an assignee and a milestone set.