Labels

Currently being worked on, expect updates soon ...

The feature has been implemented, in-review, and has has been accepted for merge. It now just needs someone (always a someone here) to formally accept the changes into the targeted branch. (This label is attached to Merge Requests, not Issues or Work Packages.)

The feature has been implemented, in-review, and waiting for someone (or a review agent) to give it a once (or twice, or thrice, ... ) over. (This label is attached to Merge Requests, not Issues or Work Packages.)

The feature has been implemented, in-review, and has received feedback. Before it can be merged, however, it needs someone (or an agent) to review the feedback, revise, and respond. (This label is attached to Merge Requests, not Issues or Work Packages.)

Involves the operations of the technology. Might be related to platform, configuration, or runtime environment.

The feature has been implemented and is waiting to be reviewed or otherwise just hanging out. (Another way of saying, almost done.)

A planning item that tracks multiple issues or merge requests. (A really big piece of scope.)

It's not clear where a particular feature or piece of functionality fits into the broader market/picture. Could someone please look at that?

What are the real-world needs? What sorts of considerations do we need to look at?

Product team has finished the commercial assessment, ready to handoff.

How does a feature fit into the broader software? How do users enter and leave? How do we onboard and offboard?

We understand how something is going to work, but how is going to function, look, and feel?

The first time you attempt to do something, you'll get it wrong, so build a prototype first. (Another way of saying we might not know how to do this.)

An answer to a question or a profound secret of existence.

A question which arose during development or something of profound philosophical importance.

The issue is currently in staging and requires review, or has appeared as part of quality assurance and needs to be addressed.

Describe how something should be done so that when you start, you don't make a mess

Issues that are queued to be worked on now (but are not currently in development)

Issues that will be tackled at some future point (probably in a month)

Issues that are currently in the planning stage