Project Management and Release Cycle

We're still finding our groove with the community fork/project management side of things, so everything here is subject to change. That said, below are some general guidelines on how the team was working/moving forward as a community:

Roadmap

We are currently working on a roadmap for our users to reference. We will update this guide when it is available.

Milestones, Releases, Packages

• A "milestone" maps 1:1 with a "release" tag. For example, v0.1.0 is a milestone we work towards that will eventually be released.
• A milestone will include cherry-picked issues across one or more projects.
• During this alpha phase of development, we will generally be using the following tagging convention:
  • v0.X.0 - a "milestone"
  • v0.X.0-alpha.X - an iteration towards a milestone. For example, v0.1.0-alpha.1 -> v0.1.0-alpha.2 -> v0.1.0 (milestone)
  • v1.0.0 will be our first "general release" (stable)

How to request features

We unfortunately cannot accept all feature requests. For the best chance at getting your feature request on the roadmap, follow the guidelines below:

• A feature request should benefit a large group of users.
• A feature request should be specific with examples, links, and any other context that helps us understand what you are asking for.
• If you see a feature you like, upvote it so we can see! The more upvotes a feature request gets, the higher the likelihood that it will make it on the roadmap.