Issue management

The API ML Squad are tracking 3 types of issues:

• - for feature requests
• - not sure about something or want to clarify
• - something is not working

Issue life-cycle

Life-cycle of the issues is tracked and managed via labels and assignee's.

Possible workflows through the life-cycle

• New -> Clarification -> Prioritization -> In Progress (Squad is working on it) -> Closed
• New -> Prioritization -> Ready for community to pick it up
• New -> Clarification -> Closed

All issues are open with label. The new label means that nobody from the API ML Squad took a look at the issue yet.

When any Squad member finds an issue with the new label the member removes the label new and assigns themselves.

• If the issue is clear and properly categorized the member assigns the Squad Lead
• If the issue is unclear the member adds the label to gather more information

When the Squad Lead is assigned an issue, the Squad decide whether this is an issue to work on in the short term.

• If the issue is going to be worked on by the Squad, the Squad Lead assigns the label
• Otherwise the Squad Lead adds the label meaning the issue can be picked up by anyone in the wider community with an interest in resolving it

When the Squad starts work on an issue the label will be added.

When the Squad resolves the issue, it is closed. This is true if the originator was part of the Pull Request reviews. If this isn't the case the squad will let the originator know that the issue was resolved.

Issue handling

The API ML Squad aim to have healthy issue log. Very old issues without response will be closed. By very old we mean issues where the squad asks the originator for any input and within a week we get no response. Thank you for your understanding.