Work on 2.3 release

[dalelane]

Release 2.3.0 is scheduled for January 2022

Detailed info:

• https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md

Kick-off:

• https://www.youtube.com/watch?v=9lJY5NcLMKY

Release branches:

• https://github.com/asyncapi/spec/tree/2022-01-release
• https://github.com/asyncapi/spec-json-schemas/tree/2022-01-release
• https://github.com/asyncapi/parser-js/tree/2022-01-release

Release notes:

• draft PR - chore(blog): add release notes for 2.3 release website#512

Progress:

• Create release branches
  • spec - https://github.com/asyncapi/spec/tree/2022-01-release
  • spec-json-schemas - https://github.com/asyncapi/spec-json-schemas/tree/2022-01-release
  • parser-js - https://github.com/asyncapi/parser-js/tree/2022-01-release
• Update release branches with new versions
  • spec - dalelane@8c52153
  • spec-json-schemas - dalelane/spec-json-schemas@9cff779
  • parser-js - dalelane/parser-js@52b4cbe
• Update release branch name in package.json
  • spec - dalelane@210f89a
  • spec-json-schemas - dalelane/spec-json-schemas@8a4b94a
  • parser-js - dalelane/parser-js@1d9f9ed
• Create draft release notes - chore(blog): add release notes for 2.3 release website#512
• Update release branches from forks
  • spec - chore: update release branch #676
  • spec-json-schemas - chore: update release branch spec-json-schemas#139
  • parser-js - chore: update release branch parser-js#426
• Notify community about release branches - slack message in #03_specification
• Check for potential release contributions
• Write release notes for new features and changes
  • Add Solace bindings - asyncapi/website@f5a5476
  • Allow servers and channels to be defined as components - asyncapi/website@7ccf866
  • Make channels optional - asyncapi/website@420ef20
  • Make regular expressions ECMA-262 compliant - asyncapi/website@4b3ad22
• Prepare pull requests to merge release branches into master
  • spec - feat: release version 2.3.0 #681
  • spec-json-schemas - feat: release for version 2.3.0 of the spec spec-json-schemas#142
  • parser-js - feat: release for version 2.3.0 of the spec parser-js#433
• Notify tsc_members about upcoming release
• Merge release branches into master
  • spec - feat: release version 2.3.0 #681
  • spec-json-schemas - feat: release for version 2.3.0 of the spec spec-json-schemas#142
  • parser-js - feat: release for version 2.3.0 of the spec parser-js#433
• 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
  • docs: update release process #722

[derberg]

@dalelane you rock mate. Feel free to also communicate it in the #specification channel in slack.

I see your checklist and I think "omg I love when someone does something I did in the past and with first iteration it is already done better" 😄

I only need more explanation on parser-js (default branch) and other related (default branch) items

[derberg]

maybe asyncapi/website#512 should include also updates to docs and other stuff on the website?
we forgot about it in 2.2 entirely, would make sense to do it this way for 2.3 and make it explicit in release process. What do you think?

[derberg]

@dalelane yo, after merging your initial release PRs to release branches, I opened these PRs:

• feat: release version 2.3.0 #681
• feat: release for version 2.3.0 of the spec spec-json-schemas#142
• feat: release for version 2.3.0 of the spec parser-js#433

there is explanation why we need them, when you will push some improvements to release instruction, please specify info about these "release" PRs, that they should not be created at the end, but since the very beginning, and monitored regularly in case some merge conflicts are discovered (can happent that some editorial change in master can cause conflict in the release branch)