We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't wait for the meeting to discuss topics that already have issues. Feel free to comment on them earlier.
Add notes here after the meeting.
The text was updated successfully, but these errors were encountered:
As I won't be there to participate, a quick update from my side.
We have one blocker for us to start moving proposals to RFC-3, which is asyncapi/spec-json-schemas#184
And right after that asyncapi/spec-json-schemas#180
I expect both to be solved right after v2.4 of the spec is out, i.e. I will finish the PR tomorrow and hopefully release it by the end of this week 🤞
After that, it is just a matter of moving changes forward little by little.
Sorry, something went wrong.
Recording of the meeting: https://www.youtube.com/watch?v=trHSXLHX05A
No branches or pull requests
Agenda
Notes
Add notes here after the meeting.
The text was updated successfully, but these errors were encountered: