Feature Tracking

To propose something new to the Zephyr Project:

  1. Start by searching existing issues to see if there is prior work on the area.

  2. If not, feel free to create a new issue of the appropriate type (Enhancement, RFC/Proposal, etc.)

You should contact an assigned owner if you’d like to discuss or contribute to an existing issue’s implementation.

Note

Previously, the project used GitHub labels to track feature-related work. You may find issues with labels like “Feature” or “Enhancement”.

These labels are deprecated for new issues, which should be of the appropriate type instead. For example, create an issue of type Enhancement instead of adding the Enhancement label to a new issue.

Roadmap and Release Plans

Project roadmaps and release plans are both important tools for the project, but they have very different purposes and should not be confused. A project roadmap communicates the high-level overview of a project’s strategy, while a release plan is a tactical document designed to capture and track the features planned for upcoming releases.

  • The project roadmap communicates the why; a release plan details the what

  • A release plan spans only a few months; a product roadmap might cover a year or more

Project Roadmap

The project roadmap should serve as a high-level, visual summary of the project’s strategic objectives and expectations.

If built properly, the roadmap can be a valuable tool for several reasons. It can help the project present its plan in a compelling way to existing and new stakeholders, to help recruit new members and it can be a helpful resource the team and community can refer to throughout the project’s development, to ensure they are still executing according to plan.

As such, the roadmap should contain only strategic-level details, major project themes, epics, and goals.

Release Plans

The release plan comes into play when the project roadmap’s high-level strategy is translated into an actionable plan built on specific features, enhancements, and fixes that need to go into a specific release or milestone.

The release plan communicates those features and enhancements slated for your project’ next release (or the next few releases). So it acts as more of a project plan, breaking the big ideas down into smaller projects the community and main stakeholders of the project can make progress on.