docs: add release process instruction #577
Conversation
|
Kudos, SonarCloud Quality Gate passed!
|
|
@magicmatatjahu as you can see it is a draft so I'm ignoring any comments on grammar as this is the last item I look at when moving out of draft, now I don't care about grammar |
Co-authored-by: Fran Méndez <fmvilas@gmail.com>
|
|
||
| ### Kick off | ||
|
|
||
| We start by creating release branches and a placeholder for release notes in the AsyncAPI Blog. |
There was a problem hiding this comment.
it feels weird that release notes would be in the blog. shouldn't they be in the repos for tools and on the website with the spec docs? ?
There was a problem hiding this comment.
Release notes for the website are there for a better presentation of the information and availability, like https://www.asyncapi.com/blog/release-notes-2.1.0. It is better to collaborate with other release contributors on a single PR
There is also always a release note in the GitHub release for a given tool, yup. There release here is for overall release summary, all features and thank you
There was a problem hiding this comment.
okay perfect, just wanted to make sure release notes weren't only in the blog
|
Kudos, SonarCloud Quality Gate passed!
|
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Release process is not final, no step by step instructions, no flow diagrams. For me it is a good foundation that we can expand and polish (or Polish) with each release