Updating based on release process
Accounting for items in https://pl-strflt.notion.site/Kubo-Release-Process-5a5d066264704009a28a79cff93062c4
Steve Loeppky committed
Jul 14, 2022 at 09:19 UTC
baa7018246ce9874469894bca620fa5a04c10d50
1 file changed
+17
-3
docs/RELEASE_ISSUE_TEMPLATE.md
+17
-3
@@ -1,8 +1,22 @@
1
> Release Issue Template
2
3
-# go-ipfs X.Y.Z Release
4
-
5
-We're happy to announce go-ipfs X.Y.Z, bla bla...
3
+# Items to do upon creating the release issue
4
+- [ ] Fill in the Meta section
5
+- [ ] Assign the issue to the release owner and reviewer.
6
+- [ ] Name the issue "Release vX.Y.Z"
7
+- [ ] Set the proper values for X.Y.Z for
8
+- [ ] Pin the issue
9
+
10
+# Meta
11
+* Release owner: @who
12
+* Release reviewer: @who
13
+* Expected RC date: week of 2022-MM-DD
14
+* Expected final release date: 2022-MM-DD
15
+See the [Kubo release process](https://pl-strflt.notion.site/Kubo-Release-Process-5a5d066264704009a28a79cff93062c4) for more info.
16
+
17
+# Kubo X.Y.Z Release
18
+
19
+We're happy to announce Kubo X.Y.Z, bla bla...
20
21
As usual, this release includes important fixes, some of which may be critical for security. Unless the fix addresses a bug being exploited in the wild, the fix will _not_ be called out in the release notes. Please make sure to update ASAP. See our [release process](https://github.com/ipfs/go-ipfs/tree/master/docs/releases.md#security-fix-policy) for details.
22