Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communicate release to support early #4689

Open
barmac opened this issue Nov 12, 2024 · 0 comments
Open

Communicate release to support early #4689

barmac opened this issue Nov 12, 2024 · 0 comments
Assignees
Labels
ready Ready to be worked on

Comments

@barmac
Copy link
Collaborator

barmac commented Nov 12, 2024

What should we do?

Communicate the release (version, changelog link, security notes if necessary) to the support at latest on Friday before the release. We could potentially automate this to be done once the release is built.
There is no need to communicate closed support related issues, but we can do that jointly.

Why should we do it?

This is required to draft the release notes early to be ready for the release public announcement.

Context:

@barmac barmac added the ready Ready to be worked on label Nov 12, 2024
@barmac barmac self-assigned this Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Ready to be worked on
Projects
None yet
Development

No branches or pull requests

1 participant