Lines Matching +full:feature +full:- +full:specific

1 .. _feature-tracking:
3 Feature Tracking
6 For feature tracking we use Github labels to classify new features and
11   block a release. This is an incremental enhancement to a feature that already
14 Feature request
19 Feature
25   A request or plan to port an existing feature or enhancement to a particular
31   A label to group other GitHub issues that are part of a single feature or unit
36 This is the formal way for asking for a new feature in Zephyr and indicating its
38 willingness to drive implementation of the feature in an upcoming release, and
41 A feature request can also have a companion RFC with more details on the feature
44 - Label new features requests as ``feature-request``
45 - The TSC discusses new ``feature-request`` items regularly and triages them.
50   - High = Next milestone
51   - Medium = As soon as possible
52   - Low = Best effort
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
60 you'd like to discuss or contribute to that feature's implementation
68 communicates the high-level overview of a project's strategy, while a release
72 - The project roadmap communicates the why; a release plan details the what
73 - A release plan spans only a few months; a product roadmap might cover a year
80 The project roadmap should serve as a high-level, visual summary of the
89 As such, the roadmap should contain only strategic-level details, major project
96 The release plan comes into play when the project roadmap's high-level strategy
97 is translated into an actionable plan built on specific features, enhancements,
98 and fixes that need to go into a specific release or milestone.