wip

.github/ISSUE_TEMPLATE/release.md

@@ -0,0 +1,61 @@
+---
+name: Release issue
+about: Create a report to help us improve
+title: ""
+labels: ':shipit: Release'
+assignees: ''
+---
+
+Release X.X.X is scheduled for XXXX
+
+### Detailed info:
+* https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md
+
+### Kick-off:
+* _link to recording of community call where the new release was started_
+
+### Release branches:
+* https://github.com/asyncapi/spec/tree/BRANCH_NAME
+* https://github.com/asyncapi/spec-json-schemas/tree/BRANCH_NAME
+* https://github.com/asyncapi/parser-js/tree/BRANCH_NAME
+
+### Release notes:
+* draft PR - https://github.com/asyncapi/website/pull/PULLREQUEST
+
+### Progress:
+- [] Create release branches
+    - [] spec
+    - [] spec-json-schemas
+    - [] parser-js
+- [] Update release branches with new versions
+    - [] spec
+    - [] spec-json-schemas
+    - [] parser-js
+- [] Update default branches with release branch name
+    - [] spec
+    - [] spec-json-schemas
+    - [] parser-js
+- [] Create draft release notes
+- [] Update release branches from forks
+    - [] spec
+    - [] spec-json-schemas
+    - [] parser-js
+- [] Notify community about release branches
+- [] Check for potential release contributions
+- [] Draft announcement blog post for new features and changes
+- [] Write release notes for new features and changes
+- [] Prepare pull requests to merge release branches into master
+    - [] spec
+    - [] spec-json-schemas
+    - [] parser-js
+- [ ] Notify tsc_members about upcoming release
+- [ ] Merge release branches into master
+    - [ ] spec
+    - [ ] spec-json-schemas
+    - [ ] parser-js
+- [ ] Write release notes for the releases on Github
+- [ ] Create releases on Github
+    - [ ] spec
+    - [ ] spec-json-schemas
+    - [ ] parser-js
+- [ ] Update RELEASE_PROCESS doc with any changes

RELEASE_PROCESS.md

@@ -301,7 +301,7 @@ The [release coordinator](#%22release-coordinator%22) should notify maintainers
 The [release coordinator](#%22release-coordinator%22) should also make sure other maintainers from other projects under the AsyncAPI GitHub organization released their packages.
 
 
-### Step 18 - notify the community
+### Step 17 - notify the community
 
 Every release of the release candidate is automatically published on the AsyncAPI Twitter account and in the releases-dedicated Slack channel.
 
@@ -310,7 +310,7 @@ Feel free to use other communication channels. Make sure that as many people as
 Make sure proper communication is sent from all the official AsyncAPI social accounts and on Slack
 
 
-### Step 19 - improve the release process
+### Step 18 - improve the release process
 
 Every release identifies new issues and ways that the process can be improved.