[
https://issues.apache.org/jira/browse/ARROW-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566851#comment-17566851
]
Jonathan Keane commented on ARROW-13062:
----------------------------------------
IMHO manual would be fine. And honestly, probably will be needed at some level
since autocreating jiras will result in a bunch of jiras that overlap (in cases
where multiple failures result from one change), or need to be duplicated
manually when one job failure is the result of multiple changes or failures.
Anyway, it's not a high priority now, we can wait until someone bumps it again
— but wanted to make sure you got credit if it was already done as part of the
work you pushed to get all of the other great stuff out
> [Dev] Add a way for people to add information to our saved crossbow data
> ------------------------------------------------------------------------
>
> Key: ARROW-13062
> URL: https://issues.apache.org/jira/browse/ARROW-13062
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
> Reporter: Jonathan Keane
> Priority: Major
>
> We should have a simple + ligthweight way to annotate specific builds with
> information like "won't be fixed until dask has a new release" or "this is
> supposed to be fixed in ARROW-XXX".
> We should find an easy, lightweight way to add this kind of information.
> Only relevant in its previous parent: -We *should not* require, ask, or allow
> people to add this information to the JSON that is saved as part of
> ARROW-13509. That JSON should be kept pristine and not have manual edits.
> Instead, we should have a plain-text look up file that matches notes to
> specific builds (maybe to specific dates?)-
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
