Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/13773
In the code implementation, these three issues are fixed in different parts
although they are in the same function. If I care the PR counts, I can submit
and fix them one by one, right? If the JIRA counts are your concern, you do not
need to assign all of them to my name and leave two of them blank. I am
completely fine with it.
Regarding the release notes, in my previous team, I have to write the APAR
for each defect fixed by myself. Each APAR should have at least three parts:
_error description_, _problem summary_, and _problem conclusion_. The customers
will read them. If they think it is related to them, they might directly
contact our L2 for understanding more details about internal changes. I do not
know who wrote the release notes for Spark, but I think enterprise customers
might have similar requirements.
When reading the source codes, I just found the bugs. What are the best
practices after finding the bugs? Most developers are kind of lazy. : ) For
developers, the easiest way is to simply fix them and write down what are bugs.
However, this does not benefit the end users. We need to see what are the
external impact for each line of changes, write separate test cases and
document them at our best. This is how my previous team works. I also think we
should follow this in Spark if we really care the conservative enterprise
customers.
You know, I just joined the community less than one year and switched to
open source development from software development for Mainframe. Let me know if
my understanding is not right. Thanks!
---
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]
