You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/02/14 21:38:17 UTC

[GitHub] srowen commented on issue #23785: [SPARK-26860][PySpark] Fix for RangeBetween docs appear to be wrong

srowen commented on issue #23785: [SPARK-26860][PySpark] Fix for RangeBetween docs appear to be wrong
URL: https://github.com/apache/spark/pull/23785#issuecomment-463808556
 
 
   @mgaido91 I think the standard practice here is to not bother with a JIRA for so-called "MINOR" changes, and I think this falls under that category. It's not a big deal but just not worth anyone's time. We have JIRA separate from Github for historical issues, so we back-filled a logic about why we even need to work on issues in two places: JIRAs describe what needs changing, and a PR is a concrete proposal for how to do it. I'd therefore define "MINOR" as anything where those are essentially the same thing. (I suppose there are other reasons you'd use a JIRA, like to track specifically which release it went into, but anything "MINOR" should probably just go to master, or else doesn't matter too much tracking its release for end-users)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org