[GitHub] [spark] HeartSaVioR edited a comment on issue #27534: [SPARK-30879][DOCS] Refine workflow for building docs

[GitBox <gi...@apache.org>]

HeartSaVioR edited a comment on issue #27534: [SPARK-30879][DOCS] Refine workflow for building docs
URL: https://github.com/apache/spark/pull/27534#issuecomment-591210981
 
 
   > There's nothing confusing to "Affected Version" on improvement type. It just targets where you want that fix to be landed.
   
   In fact we don't guide like that. For example, suppose someone found a point to improve in Spark 2.4.x - they would set "Affected Version" to be 2.4.x (or try to set it to 2.5.0 and realize it doesn't work) as it may be the only version they know about, but as I see some guides on the fly we have been guiding to the latest "unreleased" minor version which they never know about.
   
   While I don't think it represents the intention clearly on marking Affected Version on improvement, would we call it simply "the version which master branch targets to", and add it to the contribution guide? In contribution guide we only mention about bugs, no other types.

----------------------------------------------------------------
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.
 
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