Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework Github Labels #7724

Closed
neilt opened this issue Nov 18, 2023 · 4 comments
Closed

Rework Github Labels #7724

neilt opened this issue Nov 18, 2023 · 4 comments
Assignees
Labels
type:housekeeping Refactoring or other code reorganizational work

Comments

@neilt
Copy link
Contributor

neilt commented Nov 18, 2023

  1. Change all of the Github Labels to conform to the following guidelines.
  2. Make sure all Github Labels have description.
  3. Review all Issues and assign or correct labels as necessary.
GITHUB LABELS FOR ISSUES (NOT Discussions or Projects)

    ISSUE TYPE (At least 1 Required, roughly priority order, all prefixed by 'type:' in order to make label selection easy)
+-      'type:bug-accounting' (was bug:accounting) - Causes immediate accounting damage. Usually warrants a release by itself
+-      'type:dataloss' - Causes data loss. Usually warrants a release by itself
+-      'type:blocking' - Deemed "needs to be fixed before the assigned release"; unacceptable regressions or critical bugs
+-      'type:regression' - Functionality that broke over the last release cycle and should be fixed as soon as possible
+       'type:bug' - Bug that will be worked on as resources permit
+       'type:housekeeping' - Refactoring or other code reorganizational work
+-      'type:enhancement' - Improvement or new feature
+-      'type:question' - Question or support issue and not a bug

    STATUS (Optional, but recommended)
+       'assigned-to-project' - Issue resolution has been incorporated into a project
        'duplicate' - Issue is a duplicate. Needs references and will usually be immediately closed
        'invalid' - Issue isn't acknowledged as a bug/issue/enhancement by the project
+-      'has-workaround' - Issue has a workaround and may or may not be closed immediately
+       'needs-evaluation' - Status is not known at this time and needs further evaluation
+-      'waiting-for-use-case' (was use-case wanted) - In order for consideration by the project a use case is needed
        'waiting-for-review' - Issue needs review and or development
+-      'waiting-for-upstream' (was upstream) - Issue is waiting for or dependent on upstream changes
        'waiting-for-user' - Issue can't progress without additional feedback from the originator
        'wontfix' - Issue acknowledged, but won't be addressed by the project

Other changes:
- worksforme -> waiting-for-user
- all spaces in existing labels changed to hyphen
- remove 'done'
- remove 'hacktoberfest'

Legend
+ new
- To be removed
+- changed
@neilt neilt self-assigned this Nov 18, 2023
@neilt
Copy link
Contributor Author

neilt commented Nov 18, 2023

Item 1 Complete

@neilt neilt added type:housekeeping Refactoring or other code reorganizational work and removed needs-cleanup labels Nov 18, 2023
@neilt
Copy link
Contributor Author

neilt commented Nov 30, 2023

First page of issues have all been marked with a 'type:"

@neilt
Copy link
Contributor Author

neilt commented Dec 2, 2023

Second page of issues have all been marked with a 'type:"

@neilt
Copy link
Contributor Author

neilt commented Feb 13, 2024

3rd page complete. The rest of the items are getting a little baroque and I'll continue on, but closing this issue for now.

@neilt neilt closed this as completed Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:housekeeping Refactoring or other code reorganizational work
Projects
None yet
Development

No branches or pull requests

1 participant