Skip to content
This repository has been archived by the owner on Jan 24, 2018. It is now read-only.

Labels #1609

Open
david4096 opened this issue Mar 9, 2017 · 0 comments
Open

Labels #1609

david4096 opened this issue Mar 9, 2017 · 0 comments

Comments

@david4096
Copy link
Member

david4096 commented Mar 9, 2017

Discussion labels are for items that are intended to create one or more actionable issues. The discussion closes when all actionable issues it creates have been closed.

Infrastructure labels are for issues related to the scaffolding of the software, release management, and deploy processes.

Repo manager labels are for issues related to both managing the registry and the ETL processes surrounding it.

Schemas labels are for items that involve implementing a schema change, or involve discussion at the schemas level.

Bugs are for issues that result in uncaught exceptions or unexpected behavior.

Enhancement labels are for issues that improve, or add a feature.

QA labels are for issues that are related to test coverage, test performance, and generally validating and improving our inputs and outputs.

Documentation are for issues related to the support data and documentation used to support the software.

Logging are for issues related to the output of the server to administrators.

Variants, Reads, References, Sequence Annotations, and RNA should be used for issues related to the datamodel or ETL processes for each.

Client labels are for issues related to the client.

Wontfix labels are for issues that will not be closed and are left as information or discussion.

Blocked labels are for issues that cannot be closed until a change in one of our underlying dependencies has been made.

TODO: write out descriptions for labeling issues as they work their way through the review process.

If you would like to propose changes or add new labels please put it here!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant