chore(blog): announcing the work on AsyncAPI spec 3.0 release #611
Conversation
|
✔️ Deploy Preview for asyncapi-website ready! 🔨 Explore the source changes: 54f418c 🔍 Inspect the deploy log: https://app.netlify.com/sites/asyncapi-website/deploys/6228d33712d8ac00097a15c3 😎 Browse the preview: https://deploy-preview-611--asyncapi-website.netlify.app |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
|
|
||
| ## When will the release happen? | ||
|
|
||
| We are yet to arrive at a date but the community is working towards releasing this by the end of 2022. Currently, we meet every two weeks to discuss the upcoming Spec 3.0 release and share updates and you are welcome to join it! |
There was a problem hiding this comment.
please add paragraph about upcomming meeting asyncapi/community#270
maybe we will manage to merge it before
also add link to AsyncAPI calendar https://calendar.google.com/calendar/u/0/[email protected]
There was a problem hiding this comment.
Might need to push that for the next meeting, unless you are super quick @HarshCasper 😄
|
@alequetzalli have a look. Maybe you can look at my comments and already suggest proper wording to @HarshCasper |
|
Hi @derberg and @alequetzalli 👋 I have made all the suggested changes! Please have a look once you have the opportunity 😄 |
|
@jonaslagoni as you lead 3.0 meeting, you should approve this article IMHO, especially that you created a related issue |
Will do 👍 |
There was a problem hiding this comment.
Awesome @HarshCasper, just a few comments, not sure how relevant they are 🙏
HarshCasper
force-pushed
the
spec-3.0-blog
branch
3 times, most recently
from
1691f08 to
87d8e85
Compare
|
This should be ready to merge now. Thanks for all the reviews 🚀 |
There was a problem hiding this comment.
LGTM 👍
@derberg please check this change before accepting: #611 (comment)
|
@HarshCasper I see @jonaslagoni provided a link to the meeting issue, please update PR/ @alequetzalli I think it is ready for final review |
HarshCasper
requested review from
asyncapi-bot-eve,
fmvilas and
magicmatatjahu
as code owners
|
Hi @derberg It is ready for the final review now 😄 |
HarshCasper
force-pushed
the
spec-3.0-blog
branch
from
8d6e7f3 to
f39fe69
Compare
HarshCasper
force-pushed
the
spec-3.0-blog
branch
from
f39fe69 to
137b16f
Compare
HarshCasper
force-pushed
the
spec-3.0-blog
branch
from
137b16f to
4bb761a
Compare
|
@jonaslagoni Final review from @alequetzalli provided. I guess we can set publish date for tomorrow. Also please approve so we know you are happy with the article. @HarshCasper thanks a lot mate 🙏🏼 |
|
/rtm |
Description
Related issue(s)
#583