milenkovicm commented on code in PR #2724: URL: https://github.com/apache/datafusion-ballista/pull/2724#discussion_r4433023856
########## docs/source/contributors-guide/development.md: ########## @@ -234,6 +234,36 @@ DataFusion, so it is released separately from the Rust crates. See the The remaining release steps are described in the [release process](https://github.com/apache/datafusion-ballista/blob/main/dev/release/README.md). +## Backporting to a release branch + +Each release branch, such as `branch-55`, also makes minor and patch releases, so a fix or a +backward-compatible feature that has merged to `main` can reach users before the next major version. +See [Versioning and Compatibility](../user-guide/versioning.md) for what can be released this way. + +A merged change can be backported if all of these hold: + +- It does not need an entry in the [upgrade guide](#upgrade-notes). It does not break a public API, + rename or remove a configuration key or CLI flag, or change a default that alters query plans or + results. +- It does not carry the `api-change` label. +- It does not change `BALLISTA_PROTOCOL_VERSION`, and it does not change the wire format in a way that Review Comment: should we add `proto-change` label as well ? -- 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]
