This is pretty much standard semantic versioning: https://semver.org/
Maintenance branch releases are for bug fixes; minor releases have new features.
Of course at some level it all depends on judgment, too.
On Fri, Jul 24, 2020 at 1:08 PM venkat_20 wrote:
>
> Can you please elaborate why don't
Can you please elaborate why don't backport of features is not allowed?
--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
1. We don't backport features.
2. In general we don't bump dependencies, unless they are for critical bug
fixes.
3. We weight the risk of new regression vs bug fixes. To state the obvious,
we wouldn't backport a bug fix if it only affects a very small number of
use cases but require very complex
https://issues.apache.org/jira/browse/SPARK-24067
is asking to backport a change to the 2.3 branch.
My questions
- In general are there any concerns about what qualifies for backporting?
This adds a configuration variable but shouldn't change default behavior.
- Is a separate jira + pr
