alcionai / corso-roadmap

0 stars 1 forks source link

Corso roadmap

You can see the Corso project roadmap here.

Guide to the roadmap

Every item on the roadmap is an issue, with labels that indicate the following categories:

Workflow feature areas

The following is a list of feature areas which are currently tracked (intended to have support).

Data Types

The following is a list of data types which are currently tracked (intended to have support).

NOTE: Initial Corso focus is on Microsoft 365 services.

Priorities

Priority is often defined relative to other items within the same Workflow Feature Area or Data Type. It is used to express relative ordering of such related items and slotting into roadmap stages. The following is the the list of priorities currently used.

Roadmap stages

The issue Status field is used to indicate the current roadmap timing of issues. It indicates the best estimate of the expected quarter in which an item is likely to become available. The timing is advisory as priorities can and do change during planning cicles. The certainty of the projected timing decreases further out along the timeline.

Items which are not yet planned and for which no timeline is available yet are assigned Status=Future. Such items are included on the roadmap board in order to gather additional feedback. There is no guarantee that such items will be selected for development.

Released features

When a feature is released, the corresponding item is tagged with label released. Additionally, the item is closed as completed and a link is added to the changelog describing the change.

Triage process

Issues without an assigned status (Status=No Status) are still awating triage. For each of these, one of the follwing will happen:

Any feature that has not been already released, but is assigned to a quarter that has already passed, needs to go to the triage process even if the resolution is to push it to a subsequent quarter.