[jira] [Comment Edited] (ARROW-18364) MIGRATION: Update GitHub issue templates to support bug reports and feature requests
[ https://issues.apache.org/jira/browse/ARROW-18364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637424#comment-17637424 ] Todd Farmer edited comment on ARROW-18364 at 11/22/22 11:21 PM: (Moved previous comment regarding milestones to [this issue|https://issues.apache.org/jira/browse/ARROW-18381?focusedCommentId=17637500] for better tracking.) was (Author: JIRAUSER288796): (Moved previous comment regarding milestones to this issue for better tracking.) > MIGRATION: Update GitHub issue templates to support bug reports and feature > requests > > > Key: ARROW-18364 > URL: https://issues.apache.org/jira/browse/ARROW-18364 > Project: Apache Arrow > Issue Type: Task >Reporter: Todd Farmer >Assignee: Todd Farmer >Priority: Major > Attachments: image-2022-11-22-11-53-20-840.png, > image-2022-11-22-11-55-17-106.png > > > The [GitHub issue creation page for > Arrow|https://github.com/apache/arrow/issues/new/choose] directs users to > open bug reports in Jira. Now that ASF Infra has disabled self-service > registration in Jira, and in light of the pending migration of Apache Arrow > issue tracking from ASF Jira to GitHub issues, we should enable bug reports > to be submitted via GitHub directly. Issue templates will help distinguish > bug reports and feature requests from existing usage assistance questions. > It's also worth noting now that GitHub issue reporting is enabled that issues > cannot be resolved in a way that explicitly tracks the version where the > resolution was made, if the issue is tracked only in GitHub issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARROW-18364) MIGRATION: Update GitHub issue templates to support bug reports and feature requests
[ https://issues.apache.org/jira/browse/ARROW-18364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637424#comment-17637424 ] Todd Farmer edited comment on ARROW-18364 at 11/22/22 11:21 PM: (Moved previous comment regarding milestones to this issue for better tracking.) was (Author: JIRAUSER288796): (Moved previous comment regarding milestones to this issue for better tracking.) > MIGRATION: Update GitHub issue templates to support bug reports and feature > requests > > > Key: ARROW-18364 > URL: https://issues.apache.org/jira/browse/ARROW-18364 > Project: Apache Arrow > Issue Type: Task >Reporter: Todd Farmer >Assignee: Todd Farmer >Priority: Major > Attachments: image-2022-11-22-11-53-20-840.png, > image-2022-11-22-11-55-17-106.png > > > The [GitHub issue creation page for > Arrow|https://github.com/apache/arrow/issues/new/choose] directs users to > open bug reports in Jira. Now that ASF Infra has disabled self-service > registration in Jira, and in light of the pending migration of Apache Arrow > issue tracking from ASF Jira to GitHub issues, we should enable bug reports > to be submitted via GitHub directly. Issue templates will help distinguish > bug reports and feature requests from existing usage assistance questions. > It's also worth noting now that GitHub issue reporting is enabled that issues > cannot be resolved in a way that explicitly tracks the version where the > resolution was made, if the issue is tracked only in GitHub issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARROW-18364) MIGRATION: Update GitHub issue templates to support bug reports and feature requests
[ https://issues.apache.org/jira/browse/ARROW-18364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637424#comment-17637424 ] Todd Farmer edited comment on ARROW-18364 at 11/22/22 11:20 PM: (Moved previous comment regarding milestones to this issue for better tracking.) was (Author: JIRAUSER288796): While possible to map existing ASF Jira Apache Arrow project versions to GitHub milestones, there are some decisions needed to be made. The existing ASF Jira Apache Arrow versions can be seen via API [here|https://issues.apache.org/jira/rest/api/2/project/ARROW/version], and I've done an initial import to a personal GitHub repo, which can be seen via API [here|https://api.github.com/repos/toddfarmer/test-arrow-config/milestones?state=all]. Some notes: h2. Milestone name This is set to the version pulled from ASF Jira. It is not prefixed with "v" (e.g., "v1.0.0") or anything. There exist some [80+ Jira issues with fixVersions prefixed with "JS-"|https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20fixVersion%20IN(%20JS-0.3.0%2C%20JS-0.3.1%2C%20JS-0.4.0%2C%20JS-0.4.1)]. To retain this metadata, I presume we will want to create corresponding milestones. Everything else appears to have reasonable/expected numeric values for version name. h2. h2. Milestone status GitHub supports "open" or "closed" milestone statuses. ASF Jira versions have discrete "archived" and "released" boolean fields. I propose mapping anything that is either archived or released to a "closed" milestone status. The rest will be set "open". Currently, this maps the following as [open|https://api.github.com/repos/toddfarmer/test-arrow-config/milestones?state=open]: * 9.0.1 * 10.0.1 * 10.0.2 * 11.0.0 * 12.0.0 h2. Milestone date metadata GitHub milestones support a "due on" date. This is the only date field that can be set during [creation or update operations|https://docs.github.com/en/rest/issues/milestones]. GitHub also tracks dates that milestones were created, last updated, and closed - but those cannot be explicitly set. This is a little annoying, because these seem to be what get displayed in the web interface for closed milestones: !image-2022-11-22-11-53-20-840.png! Open milestones reference the "due on" date, which for open milestones, is not yet defined: !image-2022-11-22-11-55-17-106.png! While I am using the Jira version releaseDate field to map to the "due on" field in the corresponding GitHub project milestone, it's not clear that this is ever displayed or useful in the context of web views. h2. Multiple fix versions Some 314 Apache Arrow Jira issues are associated with multiple fix versions. GitHub does not allow associating an issue with multiple milestones; adding a second milestone replaces the existing milestone association. This means that 314 legacy issues will lose metadata associating with at least one version that it was associated with in Jira. Is this acceptable? Should the lowest or highest associated Jira version be used during import, if so? > MIGRATION: Update GitHub issue templates to support bug reports and feature > requests > > > Key: ARROW-18364 > URL: https://issues.apache.org/jira/browse/ARROW-18364 > Project: Apache Arrow > Issue Type: Task >Reporter: Todd Farmer >Assignee: Todd Farmer >Priority: Major > Attachments: image-2022-11-22-11-53-20-840.png, > image-2022-11-22-11-55-17-106.png > > > The [GitHub issue creation page for > Arrow|https://github.com/apache/arrow/issues/new/choose] directs users to > open bug reports in Jira. Now that ASF Infra has disabled self-service > registration in Jira, and in light of the pending migration of Apache Arrow > issue tracking from ASF Jira to GitHub issues, we should enable bug reports > to be submitted via GitHub directly. Issue templates will help distinguish > bug reports and feature requests from existing usage assistance questions. > It's also worth noting now that GitHub issue reporting is enabled that issues > cannot be resolved in a way that explicitly tracks the version where the > resolution was made, if the issue is tracked only in GitHub issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARROW-18364) MIGRATION: Update GitHub issue templates to support bug reports and feature requests
[ https://issues.apache.org/jira/browse/ARROW-18364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637424#comment-17637424 ] Todd Farmer edited comment on ARROW-18364 at 11/22/22 7:02 PM: --- While possible to map existing ASF Jira Apache Arrow project versions to GitHub milestones, there are some decisions needed to be made. The existing ASF Jira Apache Arrow versions can be seen via API [here|https://issues.apache.org/jira/rest/api/2/project/ARROW/version], and I've done an initial import to a personal GitHub repo, which can be seen via API [here|https://api.github.com/repos/toddfarmer/test-arrow-config/milestones?state=all]. Some notes: h2. Milestone name This is set to the version pulled from ASF Jira. It is not prefixed with "v" (e.g., "v1.0.0") or anything. There exist some [80+ Jira issues with fixVersions prefixed with "JS-"|https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20fixVersion%20IN(%20JS-0.3.0%2C%20JS-0.3.1%2C%20JS-0.4.0%2C%20JS-0.4.1)]. To retain this metadata, I presume we will want to create corresponding milestones. Everything else appears to have reasonable/expected numeric values for version name. h2. h2. Milestone status GitHub supports "open" or "closed" milestone statuses. ASF Jira versions have discrete "archived" and "released" boolean fields. I propose mapping anything that is either archived or released to a "closed" milestone status. The rest will be set "open". Currently, this maps the following as [open|https://api.github.com/repos/toddfarmer/test-arrow-config/milestones?state=open]: * 9.0.1 * 10.0.1 * 10.0.2 * 11.0.0 * 12.0.0 h2. Milestone date metadata GitHub milestones support a "due on" date. This is the only date field that can be set during [creation or update operations|https://docs.github.com/en/rest/issues/milestones]. GitHub also tracks dates that milestones were created, last updated, and closed - but those cannot be explicitly set. This is a little annoying, because these seem to be what get displayed in the web interface for closed milestones: !image-2022-11-22-11-53-20-840.png! Open milestones reference the "due on" date, which for open milestones, is not yet defined: !image-2022-11-22-11-55-17-106.png! While I am using the Jira version releaseDate field to map to the "due on" field in the corresponding GitHub project milestone, it's not clear that this is ever displayed or useful in the context of web views. h2. Multiple fix versions Some 314 Apache Arrow Jira issues are associated with multiple fix versions. GitHub does not allow associating an issue with multiple milestones; adding a second milestone replaces the existing milestone association. This means that 314 legacy issues will lose metadata associating with at least one version that it was associated with in Jira. Is this acceptable? Should the lowest or highest associated Jira version be used during import, if so? was (Author: JIRAUSER288796): While possible to map existing ASF Jira Apache Arrow project versions to GitHub milestones, there are some decisions needed to be made. The existing ASF Jira Apache Arrow versions can be seen via API [here|https://issues.apache.org/jira/rest/api/2/project/ARROW/version], and I've done an initial import to a personal GitHub repo, which can be seen via API [here|https://api.github.com/repos/toddfarmer/test-arrow-config/milestones?state=all]. Some notes: h2. Milestone name This is set to the version pulled from ASF Jira. It is not prefixed with "v" (e.g., "v1.0.0") or anything. There exist some [80+ Jira issues with fixVersions prefixed with "JS-"|https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20fixVersion%20IN(%20JS-0.3.0%2C%20JS-0.3.1%2C%20JS-0.4.0%2C%20JS-0.4.1)]. To retain this metadata, I presume we will want to create corresponding milestones. Everything else appears to have reasonable/expected numeric values for version name. h2. Milestone status GitHub supports "open" or "closed" milestone statuses. ASF Jira versions have discrete "archived" and "released" boolean fields. I propose mapping anything that is either archived or released to a "closed" milestone status. The rest will be set "open". Currently, this maps the following as [open|https://api.github.com/repos/toddfarmer/test-arrow-config/milestones?state=open]: * 9.0.1 * 10.0.1 * 10.0.2 * 11.0.0 * 12.0.0 h2. Milestone date metadata GitHub milestones support a "due on" date. This is the only date field that can be set during [creation or update operations|https://docs.github.com/en/rest/issues/milestones]. GitHub also tracks dates that milestones were created, last updated, and closed - but those cannot be explicitly set. This is a little annoying, because these seem to be what get displayed in the web interface for closed milestones: !image-2022-11-22-11-5
