[
https://issues.apache.org/jira/browse/HDDS-15378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-15378:
-------------------------------
Description:
Similar to Hadoop Github action labeler
(https://github.com/apache/hadoop/blob/trunk/.github/labeler.yml), let's
support labeler to automatically label based on
* Components touched (e.g. tools, client, SCM, OM, common, container, recon,
UI, etc): This can allow to reviewers to be able to see when critical
components is changed (e.g. StateMachine implementation)
* Whether it is aimed for release branch (e.g. backport patch)
* Size of the patch (s, m, xl, xlll)
* Whether review is required, jira is specified, etc
* Other labelling logic we can think of
We can check other projects as well. Please note that we also want to be
prudent in the labelling logic to prevent too many labels which will reduce the
usefulness.
was:
Similar to Hadoop Github action labeler
(https://github.com/apache/hadoop/blob/trunk/.github/labeler.yml), let's
support labeler to automatically label based on
* Components touched (e.g. tools, client, SCM, OM, common, container, recon,
UI, etc): This can allow to reviewers to be able to see when critical
components is changed (e.g. StateMachine implementation)
* Whether it is aimed for release branch (e.g. backport patch)
* Size of the patch (s, m, xl, xlll)
* Whether review is required, jira is specified, etc
* Other labelling logic we can think of
We can check other projects as well
> Support Github labeler
> ----------------------
>
> Key: HDDS-15378
> URL: https://issues.apache.org/jira/browse/HDDS-15378
> Project: Apache Ozone
> Issue Type: New Feature
> Reporter: Ivan Andika
> Priority: Major
>
> Similar to Hadoop Github action labeler
> (https://github.com/apache/hadoop/blob/trunk/.github/labeler.yml), let's
> support labeler to automatically label based on
> * Components touched (e.g. tools, client, SCM, OM, common, container, recon,
> UI, etc): This can allow to reviewers to be able to see when critical
> components is changed (e.g. StateMachine implementation)
> * Whether it is aimed for release branch (e.g. backport patch)
> * Size of the patch (s, m, xl, xlll)
> * Whether review is required, jira is specified, etc
> * Other labelling logic we can think of
> We can check other projects as well. Please note that we also want to be
> prudent in the labelling logic to prevent too many labels which will reduce
> the usefulness.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
