docs: update release process #722
Conversation
dalelane
force-pushed
the
update-release-process
branch
from
199f430 to
5259fb3
Compare
|
I think there are more things that we should include for website updates - inspired by asyncapi/website#614 but from a quick search I can see other places that would justify attention, such as the examples in https://github.com/asyncapi/website/blob/master/pages/docs/getting-started/hello-world.md |
|
/rtm |
|
Kudos, SonarCloud Quality Gate passed!
|
|
@dalelane I see you wanted to merge. It could not work as there were no approval. When you are done with updating PR basing on provided feedback remember about hitting the "arrows" icon that rerequests review and triggers notification to reviewers.
anyway, great job and now I approve 🚀 |
|
@fmvilas not sure if you had a chance to see it so pinging you so you can see great job from Dale on improving the release process |
|
/rtm |
|
This is awesome it finally got merged 👏 Awesome stuff @dalelane ! thanks |
|
now with each release goal should be to not add more steps, but remove as many manual steps as possible one by one 😅 |
|
Great stuff @dalelane 👏 |
|
🎉 This PR is included in version 2.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Updates to the document used by the release coordinator
to help smooth the process for the next release.
Contributes to: #675
Signed-off-by: Dale Lane dale.lane@uk.ibm.com