You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/11/05 02:43:58 UTC
[GitHub] [arrow] toddfarmer opened a new issue, #14593: MIGRATION: Retain issue priority?
toddfarmer opened a new issue, #14593:
URL: https://github.com/apache/arrow/issues/14593
The source ASF Jira system has a dedicated `Priority` field, for which there is no equivalent in GitHub issues. Should we use labels to retain this information as we migrate? For example:
* `Priority: 1`
* `Priority: 2`
I personally prefer numeric priorities over strings such as `High` or `Urgent`, because it makes relative priority readily apparent without having to consult the list of possible values (and interpreting whether High or Urgent has higher priority). But I'm open to suggestions if other values are preferred.
--
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: github-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] rok commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
rok commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1374888564
If there are no objections I'll create the last proposed labels when I start the migration sometime this week.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] rok commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
rok commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1374244690
I think these labels are used but not consistently so not sure if they are net good.
As for release-blocker - it could be skipped in favor of convention that everything within a milestone is a blocker for it.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] raulcd commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
raulcd commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1375324641
@rok I have created the three labels as we are going to need the `Priority: Critical` in preparation for the release. I am going to start asking people to mark any release blocker with it on the mailing list and Zulip.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] wjones127 commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
wjones127 commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1374344293
> it could be skipped in favor of convention that everything within a milestone is a blocker for it.
Not sure about that. I think we often tag issues with the release to indicate that we would *like* to get that included, but not that it's absolutely necessary. It's helpful to have a tag that distinguishes what's nice to have and what's necessary. But maybe there's a better way to do that?
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] rok commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
rok commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1376061748
I suppose this is resolved then.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] rok commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
rok commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1363546486
I like the idea of just bringing in the Jira priorities as labels. We would then have:
* Priority: Blocker
* Priority: Major
* Priority: Minor
* Priority: Trivial
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] wjones127 commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
wjones127 commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1374210322
I'm skeptical those labels 4 labels are actually used. I'm personally only in favor of bringing over labels that are used in practice. Realistically, I think we only need two labels:
* release-blocker: which tells us we cannot bump this issue to the next release milestone
* critical-fix: which tells us we should prioritize fixing this over most other things. Defined as is in https://lists.apache.org/thread/s49bkj8ckgcjvjskhhz26xy1xscrswdp
I'm not familiar with any practice that involves Major/Minor/Trivial, and other commenters on this issue seem to be saying the same thing.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] toddfarmer commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
toddfarmer commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1361860639
cc @rok to evaluate what needs done here.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] jorisvandenbossche commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
jorisvandenbossche commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1361553685
Short term, we can maybe "just" (assuming this is not too hard to set up) map the priority to labels? And then we can still later see if we want to keep all of them or only the blocker/critical ones?
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] toddfarmer commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
toddfarmer commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1304617338
[Example](https://github.com/toddfarmer/test_import/issues/44):
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] rok closed issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
rok closed issue #14593: MIGRATION: Retain issue priority?
URL: https://github.com/apache/arrow/issues/14593
--
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: issues-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] rok commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
rok commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1374436282
Yeah, having an explicit label there will make it easier for the release work indeed. We would then migrate the following labels from Jira:
* Priority: Critical
* Priority: Blocker
* good-second-issue
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] toddfarmer commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
toddfarmer commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1304616971
As a note, it is possible to [create custom fields in GitHub projects](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects), which would allow explicit `Priority` field definition and tracking. That said, it seems it is not possible to directly query project custom fields for issue searching, except within the context of a specific project.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] raulcd commented on issue #14593: MIGRATION: Retain issue priority?
Posted by GitBox <gi...@apache.org>.
raulcd commented on issue #14593:
URL: https://github.com/apache/arrow/issues/14593#issuecomment-1310302380
I agree with @jorisvandenbossche here. The `Priority: Blocker` is really helpful for release management purposes and maybe another for work prioritization but the rest of the levels don't seem necessary in my opinion.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org