assignUser commented on issue #14507: URL: https://github.com/apache/arrow/issues/14507#issuecomment-1293896049
I have added some examples/details about task lists in #14520 > still think there's value in knowing the issue type of an issue migrated from ASF Jira. If not "sub-task" as a label, should we not include an explicit type label? Should we call it a "task", effectively elevating it from sub-task to task? eh, sub-tasks are marked as such by the "tracked in"-badge, I don't think that is worth another label. For the other types labels make sense. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
