Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13773
Of course, you can always describe several impacts of one logical issue in
one JIRA. Nobody disagrees that clear and complete descriptions are good, but
that's orthogonal. Surely you provide title and description in release notes?
The real test is, would you ever fix one but not the other? apply a patch
for one and not another? If so, then yeah they should probably be different
issues, and different patches to address them. But here you made one change,
so, I can't take the fix for one without the other, which is why I don't quite
get the argument. Also, if they're tracked as separate issues, users could miss
the connection between them (though you can link JIRAs).
We also have a minor problem with some organizations rewarding JIRA and PR
count. I don't think that's an issue here, but would like to set a certain
standard about this practice.
It's up to your judgment here, but keep it in mind.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
