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

Release note for deployments to production #3069

Open
LeandraH opened this issue Feb 5, 2025 · 0 comments · May be fixed by #3079
Open

Release note for deployments to production #3069

LeandraH opened this issue Feb 5, 2025 · 0 comments · May be fixed by #3079
Assignees
Labels
CI/CD Changes in the CI not-testable Not testable by our tester ready Task

Comments

@LeandraH
Copy link
Contributor

LeandraH commented Feb 5, 2025

Is your feature request related to a problem? Please describe.
Currently, our release notes get posted to the releases channel on Mattermost whenever we do a release, i.e. deploy from the main branch to either beta or prod. We don't really every deploy from main to prod, though; we instead promote the builds from beta to prod, and that doesn't send release notes to Mattermost.

This used to not be a problem when we had rolling releases because everybody knew that whatever was being released to beta would released to prod a week later (or if something failed, two weeks later). Without the rolling releases, non-developers do not have an easy way of seeing what has been released to production recently. We should change that.

Describe the solution you'd like
Ideally, we change the promotion workflow to also update Mattermost.

Describe alternatives you've considered
We could manually post on Mattermost, which seems annoying and will probably get forgotten. Or we could do deployments from the main branch to production, but then we might deploy something that hasn't been on beta yet.

Additional context
This came up because the Social and Service teams wanted to know what has gone live recently. They shouldn't have to ask for each issue :)

@LeandraH LeandraH added CI/CD Changes in the CI Task labels Feb 5, 2025
@steffenkleinle steffenkleinle moved this to Next Up in team-app Feb 5, 2025
@steffenkleinle steffenkleinle added not-testable Not testable by our tester ready labels Feb 5, 2025
@bahaaTuffaha bahaaTuffaha self-assigned this Feb 10, 2025
@bahaaTuffaha bahaaTuffaha moved this from Next Up to In Progress in team-app Feb 10, 2025
@bahaaTuffaha bahaaTuffaha linked a pull request Feb 11, 2025 that will close this issue
@bahaaTuffaha bahaaTuffaha moved this from In Progress to In Review in team-app Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD Changes in the CI not-testable Not testable by our tester ready Task
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

3 participants