Skip to content

Commit

Permalink
Update release-template.md to consistently notify comms team (#3908)
Browse files Browse the repository at this point in the history
Trying to find a way for the marketing/comms team to get early notification, consistently, that a new release will happen.

@romac or Luca (not tagging b/c of holidays) if you prefer other approaches then happy to go with something else.

Signed-off-by: Adi Seredinschi <adi@informal.systems>
  • Loading branch information
adizere authored Mar 26, 2024
1 parent a1fa6ee commit a1c4360
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/release-template.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,4 +20,4 @@ v without deliberation
- [ ] Create a new release in the changelog, using [`unclog`](https://github.com/informalsystems/unclog)
- If doing a release candidate (`rc`) version, then skip the `unclog release` step
- [ ] Reassign unfinished issues of previous milestone to the next milestone
- [ ] Notify the comms team about the pending new release and [prepare a message](https://www.notion.so/informalsystems/Communications-pipeline-b8c0eeb71dc24203a048fa6ccf189e1a?pvs=4) to announce it
- [ ] Notify the comms team about the pending new release by tagging [@isa-belch](https://github.com/isa-belch) as a reviewer here

0 comments on commit a1c4360

Please sign in to comment.