mocobeta commented on issue #6:
URL:
https://github.com/apache/lucene-jira-archive/issues/6#issuecomment-1172396097
Pre-set labels should be fixed before migration since we need to attach them
to migrated issues in the import scripts.
Label texts can be changed afterward, but they'd have to be manually changed
(we are not allowed to call GitHub API on ourselves) and it'd be bothersome and
error-prone.
I'd propose four label families:
- `type` : Jira's "Issue Type"
- `type:bug` for a bug report. The corresponding Jira issue type is `Bug`.
- `type:enhancement` for an enhancement. The corresponding Jira issue
types are `New Feature`, `Improvement`, and `Wish`.
- `type:task` for a task. The corresponding Jira issue type is `Task`.
- `type:test` for test-related issues. The corresponding Jira issue type
is `Test`
- `fixVersion` : Jira's "Fix Version(s)"
- e.g.: `fixVersion:9.2.0`
- `affectsVersion`: Jira's "Affects Version(s)"
- e.g.: `affectsVersion:9.0.0`
- `component` : Jira's "Component(s)"
- e.g.: `component:module/core/index`, `component:module/analysis`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
