AsyncAPI spec v3.0.0 release journal

[smoya]

This issue keeps a journal of the release process for AsyncAPI spec v3.0.0.
The journal format is gonna be accomplished by making GH comments. There is no particular format on those but feel free to suggest it if you feel it is necessary.

The main goals for such thing are:

1. To have a common reference point for all people interested in keeping up with this current release process.
2. To use it for building up documentation for the process of releasing versions that include breaking changes. A guideline as an outcome.
3. To eventually and optionally write a blog post or a series of blog posts.

There is now an issue where we track progress on v3: asyncapi/spec#691, However this journal will stay here and will be used for tracking events and news regarding this release.

[smoya]

During today's SIG Meeting @jonaslagoni is gonna suggest a new recurring meeting for those interested in following and/or working on the v3.0.0 release efforts.

The creation of a "Working Group" might also be suggested so we have a group of people that will work on the release process of this v3.0.0 version.

More details can be found in #157

[alequetzalli]

oh wow, this is nice!!

[jonaslagoni]

@smoya and I went down a bit of a rabbit hole that was triggered by referencing behavior, gathered everything under a blog post for visibility on the problem - asyncapi/website#461

This resulted in 3 new issues for both spec and parser-js library.

[smoya]

Parser-JS implementing the Parser-API (asyncapi/parser-js#401) could be considered a thing now that we would need to adapt the parser for 3.0.0 changes.

We would like to get a list of pros/cons about adopting the Parser-API, for later on presenting them to the community so we can all make a decision. In order to do some brainstorming so we can get such a list, we (@jonaslagoni and I) have scheduled a public meeting. Therefore we have asked @boyney123 and @alequetzalli to join us as well and they confirmed.

Meeting has been scheduled for Monday Dec 6, 8am PST, and it will be included as part of our Contributor-first meeting, so will be streamed via Youtube, Twitch, Twitter...

EDIT 7 Dec 2021:

During the meeting, we came out with some pros/cons about adopting Intent-driven API + Parser-API for our parsers. Here is the link (you can also add your thoughts!) https://hackmd.io/AYyrgWMQRXuOKl_VsxUbCA

[smoya]

@derberg has started a new GH Discussion here for "Start collecting AsyncAPI use cases".
This is extremely valuable for understanding what should v3.0.0 should cover, also what could be postponed to future versions, and how changes that are candidates to be in v3.0.0 could affect others.

[smoya]

I updated asyncapi/parser-js#401 reflecting all collected pros/cons of implementing the Intent-Driven API and Parser-API. So now the question we need to answer asap in there is, should we move forward?

[jonaslagoni]

A final suggestion for the bi-weekly community meeting added and shared: #157 (comment)

Suggested starting date Wednesday 19th, 5 PM CET

[smoya]

A final suggestion for the bi-weekly community meeting added and shared: #157 (comment)

Suggested starting date Wednesday 19th, 5 PM CET

The meeting happened and it seems it had a good acceptance because people were very enthusiastic about keeping having more.
The meeting was recorded and can be watched on Youtube.

As a result of it, several issues were created so we can follow up and progress on several topics:

• On one side, @jessemenning suggested to Increase frequency of Spec 3.0 meeting from biweekly to weekly spec#690.
• Also to Use Version 3 milestone to triage potential inclusions in AsyncAPI version 3 spec#692.
• @jonaslagoni ended up creating a global issue to track the Work on 3.0 release spec#691.

Thanks to @damaru-inc, @aricart, @magicmatatjahu, @boyney123, @dalelane, @jessemenning, @smoya, and @jonaslagoni (and @fmvilas via chat!) for participating, but also to all people connected on all streaming platforms.

[smoya]

More "Spec 3.0" Meetings happened during last weeks. I won't add a new update every time there is another one but instead, I'm leaving here this link where you can find all of the issues we created per event. They include the agenda, video recordings, live chats and notes.

https://github.com/asyncapi/community/issues?q=is%3Aissue+is%3Aclosed+%22Spec+3.0+Meeting%22

[jonaslagoni]

I decided to add a migration guide for 3.0: asyncapi/website#660

What this evolves into is hard to say, let's see. However, we needed a place to write all the migration guides down so tools such as converters can be accurately adapted.

[smoya]

parser-js v2 has been released as beta. As per today, latest version is v2.0.0-next-major.6.

This is unblocking development of Spec v3.0.0 features, and the idea is to release this new parser-js version soon and with enough time to have it tested heavily before releasing Spec v3.0.0.

[jonaslagoni]

As the release process for v3 is complete I am gonna close down this issue.