Skip to content
New issue

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

[WFLY-15016] Reactive Messaging and AMQ Streams support #414

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kabir
Copy link
Contributor

@kabir kabir commented Jul 15, 2021

@kabir kabir force-pushed the WFLY-15016-support-amq-streams branch from 7e95083 to c046ce6 Compare August 2, 2021 12:26
Copy link

@fabiobrz fabiobrz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @kabir - I had a quick look and dropped a couple of comments and questions.
Feel free to let me know what you think.

* mailto:{email}[{author}]

=== QE Contacts
TBD

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can exceptionally add 3 contacts, BTW 😄 - Jan Stourac, Miroslav Novak and myself.


=== Non-Requirements

TBD as we identify pain points during testing. I am not intimately familiar with Kafka/AMQ Streams.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any updates to resolve this section? Anything we should mention? BTW I see there's an open bug affecting the implementation, i.e. https://issues.redhat.com/browse/WFWIP-367

This is covered by the linked <<Related Issues>>.

== Release Note Content
////

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This proposal is mostly about testing and documentation, so just asking: are there no community release notes that can be mentioned here? Maybe those of the related issues here too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants