Update release-checklist.md#777
Conversation
Adding todo to update community through email/discord/slack
Codecov Report
@@ Coverage Diff @@
## master #777 +/- ##
=======================================
Coverage 68.75% 68.75%
=======================================
Files 64 64
Lines 3831 3831
Branches 701 701
=======================================
Hits 2634 2634
Misses 866 866
Partials 331 331 Continue to review full report at Codecov.
|
| - [ ] `git branch -D master-test` | ||
| - [ ] `git push origin :master-test` | ||
| - [ ] Announce availability in #engineering and on the forum here: https://forum.blockstack.org/c/releases (Include a link to the changelog) | ||
| - [ ] Announce availability to the community via Jenny Mith <jenny@blockstack.com> and Mitchell Cuevas <mitchell@blockstack.com>. Provide a succinct list of changes, the like to the changelog and latest release as well as a desired date for the community update. |
There was a problem hiding this comment.
Should it be "the link to the changelog" instead?
There was a problem hiding this comment.
I think a link is not sufficient enough. They want two things mainly: 1) a date when this should go out to the community and 2) a message that should go out to the community. Just providing a link to the changelog won't be enough. We should clearly community in brief why and what was changed as well as what the impact is. It's something that will be really hard for Jenny or Mitchell to get from the pure technical changelog is my argument.
There was a problem hiding this comment.
I was only referring to the spelling error: "like" in place of "link". Otherwise looks good to me.
There was a problem hiding this comment.
Hah, of course, that needs to be fixed :)
| - [ ] `git branch -D master-test` | ||
| - [ ] `git push origin :master-test` | ||
| - [ ] Announce availability in #engineering and on the forum here: https://forum.blockstack.org/c/releases (Include a link to the changelog) | ||
| - [ ] Announce availability to the community via Jenny Mith <jenny@blockstack.com> and Mitchell Cuevas <mitchell@blockstack.com>. Provide a succinct list of changes, the like to the changelog and latest release as well as a desired date for the community update. Consider doing an AMA with the community. |
There was a problem hiding this comment.
Is the AMA meant to happen for every release?
There was a problem hiding this comment.
No, optional. I think this would require a judgement call on the releaser, ie "is this important enough to organize an AMA for"? Should I point that out as well?
There was a problem hiding this comment.
I think it should be clear when that should happen. i.e. Consider doing an AMA on major/breaking releases.
There was a problem hiding this comment.
Makes sense, adding that
2 participants
Description
Adding todo to update community through email/discord/slack. This will allow broader community awareness for updates.
Jenny and Mitchell are aware of and approved this addition. They also suggested to provide more lead time for high impact release and engage with them earlier on to craft a more comprehensive community update.
Type of Change
Does this introduce a breaking change?
No
Are documentation updates required?
No