Hi everyone,
I added a new flag for PR's, "release note needed”. We should update the release process to clearly note such changes, so users are aware of incompatible dependency changes. Since merged PR’s are closed, the release manager has to check that we point out all of those to avoid disruptions in production setups. Your thoughts? Better ideas? —Alex -- *Scalytics* Software that holds the line. Are you ready <https://ai-ready.scalytics.io>? www.scalytics.io <http://www.scalytics.io> | /company/scalytics <https://www.linkedin.com/company/scalytics> | @scalyticsAI <https://x.com/scalyticsAI> -- Please consider the environment before printing this email -- Disclaimer: The content of this message is confidential. If you have received it by mistake, please inform us by an email reply and then delete the message. It is forbidden to copy, forward, or in any way reveal the contents of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet. Therefore, the sender will not be held liable for any damage caused by the message.
