Personally, I watch the "iss...@arrow.apache.org" mailing list, which only
sends one email for a new JIRA creation to have an overview of only new
JIRAs (and based on that I subscribe to JIRAs that interest me to get more
email notificaitons).
So I have a slight preference that people keep using th
I personally filter all JIRA emails to the trash--agree that it's too noisy
to pay attention to. The zulip chat app that Ursa Labs hosts (happy to
invite anyone to it, just email me) has a reasonable threaded view of JIRA
activity that I rely on. It's not perfect either but it's much more
manageabl
I would love that also!
Atm we need to:
* add the tag to the jira issue
* add the component in the dropdown for components
* add the component to the PR
In case of multiple components, the above is per component, per PR.
IMO we should only have to select the component from one place, which IMO
s
I am all for automation. I'll see if I can carve out some time to work on
that next week.
Neal
On Fri, Feb 5, 2021 at 8:13 AM Wes McKinney wrote:
> It occurs to me we could (relatively) easily program a bot to apply
> these "title tags" automatically based on what's in the Component
> field. Wh
It occurs to me we could (relatively) easily program a bot to apply
these "title tags" automatically based on what's in the Component
field. What do you think?
On Fri, Feb 5, 2021 at 10:09 AM Neal Richardson
wrote:
>
> Hi folks,
> Just a reminder to please make sure your JIRA issue titles start
Hi folks,
Just a reminder to please make sure your JIRA issue titles start with the
subproject/language in square brackets ([Rust], [Python], etc.). If you're
reviewing or triaging issues that others have reported, please do clean
them up. While it is technically redundant to the component field,
