Release Glee v1 and add support for spec 3.0

[fmvilas]

(This issue has been created with the purpose of grouping the tasks below. Please comment on these issues instead.)

Scope

• upgrade parser to version 3(next-major) #409
• Authentication layer for glee, support for different authentication frameworks  #377
• AsyncAPI spec v3 support in Glee #457
• Show a warning if glee can't process a received message #558
• provide a flag to disable the logging of inbound and outbound messages #557
• Client security doesn't work with v3 of the spec #556
• use the correct bindings for http client #553

Optional

• Routing Messages Based on Payload Schemas for Channels with Multiple send/receive Operations #563
• support parameters for channel address. #555

[Amzani]

@fmvilas I suggest to

• Remove Add required support for existing adapters #514 from the scope. As discussed with @KhudaDad414 and @Souvikns we can release Glee v1 with Spec 3.0 and Auth (Authentication layer for glee, support for different authentication frameworks  #377).
• Convert Add required support for existing adapters #514 to a Bet that we deliver in the next cycle

[fmvilas]

Sure, that should work 👍

[KhudaDad414]

@fmvilas
I suggest the following issues for the next cycle:
#558
#557
#556
#555
#553
#563
#411

[fmvilas]

I'd mark the following as optional for the next cycle because they're not trivial:

• support parameters for channel address. #555
• Routing Messages Based on Payload Schemas for Channels with Multiple send/receive Operations #563

And clarify who's gonna own #411 and #556 because @oviecodes expressed interest too.

[oviecodes]

I'm on #411 @fmvilas , @Souvikns is taking #556 .

[fmvilas]

Thanks, @oviecodes 🙏

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️