villebro commented on issue #31408: URL: https://github.com/apache/superset/issues/31408#issuecomment-2542020485
> > I will add a section to cover this. > > Thanks. Please consider any necessary changes to [RELEASING/README.md](https://github.com/apache/superset/blob/master/RELEASING/README.md). @michael-s-molina I think it's actually mostly relevant for the SIP process, rather than the release process. Any major breaking changes or new advanced features that affect how Superset is deployed may affect how the Docker image is built, our Docker Compose flows, and ultimately the Kubernetes deployment model. A few examples: - **Global Async Queries using Websockets**: there is an unofficial `oneacrefund/superset-websocket` image that requires an extra deployment on Kubenetes, which is currently supported by Helm. In retrospect, [[SIP-43]](https://github.com/apache/superset/issues/9190) should have addressed how this would be supported in all the currently existing deployment models. - **Addition/removal of a critical component**: Assuming we were to replace Celery Beat with another scheduler, that would need to be considered during the SIP review, as it would likely require changing what the scheduler [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) looks like. Therefore, major changes should be handled as follows: 1. Infra related breaking changes will need to be raised during the SIP process to ensure they're considered before the vote. 2. Support for accepted SIPs will need to be added to the dev version of the Operator, so that a clear warning/error can be emitted if the chosen Superset version is unsupported. Note that will be easier to support in the Operator, but more difficult in Helm, as Helm doesn't easily support this type of logic. 3. Once the new version is released that introduces the breaking change, the affected versions of the operator should be patched with logic to check if they are compatible with the newly introduced version or not. Anyway, I'll cover all of this in the new section. -- 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]
