Tweet about finished deployments again
gitlab-org/release-tools@afeaf960 limited announcing a deployment to those cases where downtime is needed (probably related to #56 (comment 56602997)).
Tweeting that a deployment is finished is still part of the checklists:
- https://gitlab.com/gitlab-org/release-tools/blob/da4670786eb3df5fdc4f0a702f48a110317a8b97/templates/monthly.md.erb#L105
- https://gitlab.com/gitlab-org/release-tools/blob/da4670786eb3df5fdc4f0a702f48a110317a8b97/templates/monthly.md.erb#L197
- https://gitlab.com/gitlab-org/release-tools/blob/da4670786eb3df5fdc4f0a702f48a110317a8b97/templates/monthly.md.erb#L269
- https://gitlab.com/gitlab-org/release-tools/blob/da4670786eb3df5fdc4f0a702f48a110317a8b97/templates/monthly.md.erb#L352
- https://gitlab.com/gitlab-org/release-tools/blob/da4670786eb3df5fdc4f0a702f48a110317a8b97/templates/security_patch.md.erb#L60
- https://gitlab.com/gitlab-org/release-tools/blob/da4670786eb3df5fdc4f0a702f48a110317a8b97/templates/patch.md.erb#L56
However it didn't happen recently: https://twitter.com/search?l=&q=deployed%20from%3Agitlabstatus%20since%3A2018-01-01%20until%3A2018-12-01&src=typd
I think we should still do this because it gives users the chance to have a look at new features on gitlab.com (and find bugs) before they are officially released and also to verify bug fixes.
Edited by Inactive Account