comphead opened a new issue, #22765:
URL: https://github.com/apache/datafusion/issues/22765
Originally raised by @mbutrovich
The current `release_management.md` documents the mechanics of backporting
(cherry-pick, PR title, examples) but does not state which kinds of changes are
appropriate for a release branch — only the general line "Only targeted,
low-risk fixes should be added."
This leaves contributors and release managers re-litigating the same
case-by-case questions on every patch release (Is this perf fix in scope? What
about a refactor that fixes a latent bug? A new error message?), and the
answers are not discoverable to first-time backporters.
This proposal adds a written Backport Criteria section - modeled on Apache
Spark's versioning policy that enumerates what is eligible, what is not
recommended, how behavior-changing fixes are handled, and who decides. The goal
is to set a clear, predictable bar for release branches, reduce churn during
stabilization, and make the release manager's gatekeeping role explicit rather
than tacit.
The proposal is a easy start doc, ported from Apache Spark, however we need
to consider DataFusion family of downstream projects
FYI @milenkovicm @gabotechs @andygrove @timsaucer @adriangb
The context:
_Originally posted by @comphead in
[#21080](https://github.com/apache/datafusion/issues/21080#issuecomment-4603994536)_
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
