nealrichardson opened a new issue, #14546: URL: https://github.com/apache/arrow/issues/14546
@assignUser said: "I think importing all issues regardless of status makes sense as there is no cost to us ( excl. migration script run time) and it has the benefits of keeping all previous discussion and knowledge in one place e.g. for new (and old but they might know to also check jira) contributors to look through prior to opening an issue or for the directional links between issues." To argue the other side: whether or not there is no cost (I'm not sure I agree), I'm not sure there's any benefit, particularly given that we can keep the Jira issues where they are as read-only. They're only a click away on the old merged github PRs, and easily findable from the commit message prefixes. If we duplicate all of that in GitHub Issues, would we also go back and rewrite all of the past commit messages? If not, what's the point of duplicating the information in (closed) GitHub Issues? -- 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]
