PR labeling standard

[j4w8n]

To keep the community updated on a PR's status, we are implementing the following labels and looking for community feedback.

• A PR is not required to go through any or all positive steps on its way to being merged.
• The labeling system is not strictly required for every PR; but this should be an exception, not the rule.
• New PRs will not be automatically given a default label.

Labels

• considering - Being talked about; whether to accept or decline.
• declined - Not planned. An explanation may be provided. Perhaps not needed, since one would simply close the PR with a comment.
• accepted - Planned. The PR may be approved and/or assigned.
• reviewing - A member or maintainer has started the process of reviewing the code.
• testing - A member or maintainer has started the process of testing the code.
• abandoned - Rejected for some reason, after being accepted. An explanation must be provided.
• queued ready - Waiting to be merged. The PR must be approved.
• merged - Self-explanatory, and we may not even use this label.
• reverted - PR was reverted. An explanation must be provided.

We are still working through the details of the label implementation. e.g. If a PR requires considering, once it's declined or accepted it makes sense to remove the considering label. However, if a PR is accepted, that label might remain when subsequent labels, like reviewing or testing, are added; resulting in two or more labels on a PR at once.

[j4w8n]

Already thinking that ready would be more clear than queued.

[j4w8n]

I wonder if some "waiting" labels would be appropriate?

• waiting: author, if we're waiting on them to make changes, etc
• waiting: upstream, if we're waiting for a fix from a package that we depend on