Updating blog entry request section
Steve Loeppky committed
Aug 8, 2022 at 11:53 UTC
dbe4e6cf243ea4d1ef0cc1e6ffc86c3852526293
1 file changed
+4
-4
docs/RELEASE_ISSUE_TEMPLATE.md
+4
-4
@@ -105,13 +105,13 @@ Checklist:
105
- [ ] use the artifacts built in CI for dist.ipfs.io: `wget "https://ipfs.io/api/v0/get?arg=/ipns/dist.ipfs.io/kubo/$(curl -s https://dist.ipfs.io/kubo/versions | tail -n 1)"`
106
- [ ] to [arch](https://www.archlinux.org/packages/community/x86_64/go-ipfs/) (flag it out of date)
107
- [ ] Cut a new ipfs-desktop release
108
- - [ ] Submit [this form](https://airtable.com/shrNH8YWole1xc70I) to publish a blog post, linking to the GitHub release notes
108
+ - [ ] Get a blog post created.
109
+ - Make a request in Filecoin Slack channel #shared-pl-marketing-requests
110
+ - Request should take the form of "We'd like a Kubo release notes blog entry that links to the release notes https://github.com/ipfs/kubo/releases/tag/v0.Y.0"
111
- [ ] Broadcasting (link to blog post)
110
- - [ ] Twitter (request in Slack channel #pl-marketing-requests)
111
- - [ ] Matrix
112
+ - [ ] Twitter (request in Filecoin Slack channel #shared-pl-marketing-requests)
113
- [ ] [Reddit](https://reddit.com/r/ipfs)
114
- [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements)
114
- - [ ] Announce it on the [IPFS Users Mailing List](https://groups.google.com/forum/#!forum/ipfs-users)
115
- [ ] **Post-Release**
116
- [ ] Merge the `release` branch back into `master`, ignoring the changes to `version.go` (keep the `-dev` version from master).
117
- [ ] Create an issue using this release issue template for the _next_ release.