Lines Matching full:a
10 Changes to existing features that are not considered a bug and would not
11 block a release. This is an incremental enhancement to a feature that already
15 A request for the implementation or inclusion of a new unit of functionality
20 A committed and planned unit of functionality with a detailed design and
22 and must be vetted and discussed in the TSC before a target milestone is set.
25 A request or plan to port an existing feature or enhancement to a particular
26 hardware platform. This ranges from porting Zephyr itself to a new
27 architecture, SoC or board to adding an implementation of a peripheral driver
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
37 importance to the project. Often, the requester may have a readiness and
41 A feature request can also have a companion RFC with more details on the feature
42 and a proposed design or implementation.
67 they have very different purposes and should not be confused. A project roadmap
68 communicates the high-level overview of a project's strategy, while a release
69 plan is a tactical document designed to capture and track the features planned
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
83 If built properly, the roadmap can be a valuable tool for several reasons. It
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
98 and fixes that need to go into a specific release or milestone.
101 project' next release (or the next few releases). So it acts as more of a
106 have an assignee and a milestone set.